🚀 DAY 5 OF LAUNCH WEEK: Introducing Socket Firewall Enterprise.Learn more →
Socket
Book a DemoInstallSign in
Socket

yapstone-disputes

Package Overview
Dependencies
Maintainers
1
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

yapstone-disputes

bundlerRubygems
Version
1.0.0
Version published
Maintainers
1
Created
Source

yapstone-disputes

Yapstone - the Ruby gem for the YapStone Dispute Composite Service

This service provides a Dispute engine that enables a Marketplace to manage Disputes and Dispute related objects like Evidences on processed Payments.

This SDK is automatically generated by the OpenAPI Generator project:

  • API version: v1
  • Package version: 1.0.0
  • Build package: org.openapitools.codegen.languages.RubyClientCodegen

Installation

Build a gem

To build the Ruby code into a gem:

gem build yapstone-disputes.gemspec

Then either install the gem locally:

gem install ./yapstone-disputes-1.0.0.gem

(for development, run gem install --dev ./yapstone-disputes-1.0.0.gem to install the development dependencies)

or publish the gem to a gem hosting service, e.g. RubyGems.

Finally add this to the Gemfile:

gem 'yapstone-disputes', '~> 1.0.0'

Install from Git

If the Ruby gem is hosted at a git repository: https://github.com/GIT_USER_ID/GIT_REPO_ID, then add the following in the Gemfile:

gem 'yapstone-disputes', :git => 'https://github.com/GIT_USER_ID/GIT_REPO_ID.git'

Include the Ruby code directly

Include the Ruby code directly using -I as follows:

ruby -Ilib script.rb

Getting Started

Please follow the installation procedure and then run the following code:

# Load the gem
require 'yapstone-disputes'

api_instance = Yapstone::AuthenticationApi.new
grant_type = 'client_credentials' # String | To do OAuth2 authentication, you must indicate the grant type, then adhere to it structurally. Yapstone API endpoints authenticate with OAuth2 and the grant type client credentials. This type of authentication is used to access resources on your own system rather than access a user's resources. 
authorization = 'Basic SGxkdU5OcU1xMzBUZ0djYUpDWVpIWVRsejJjQUJlSHo6YkdIeWNpWXVibzNVTXZLRA==' # String | Provide client_id:client_secret as base64 encoded basic auth. 

begin
  #Authenticate Partner
  result = api_instance.authenticate_partner(grant_type, authorization)
  p result
rescue Yapstone::ApiError => e
  puts "Exception when calling AuthenticationApi->authenticate_partner: #{e}"
end

Documentation for API Endpoints

All URIs are relative to https://api-prod-sandbox.yapstone.com/v1/dispute

ClassMethodHTTP requestDescription
Yapstone::AuthenticationApiauthenticate_partnerPOST /v1/oauth2/client_credential/accesstokenAuthenticate Partner
Yapstone::DisputesApiaction_by_dispute_idPATCH /disputes/{id}/actionAction to perform on the dispute - two values are supported - ACCEPT or CONTEST
Yapstone::DisputesApicreate_disputePOST /disputesCreate a dispute [Test Only]
Yapstone::DisputesApifinal_disposition_by_dispute_idPATCH /disputes/{id}/finalDispositionFinal disposition to be set on the dispute - two values are supported - WON or LOST
Yapstone::DisputesApiget_disputeGET /disputes/{id}Fetch a single dispute
Yapstone::DisputesApiget_dispute_eventsGET /disputes/{id}/eventsFetch the dispute events associated with a dispute
Yapstone::DisputesApiupdate_statusPATCH /disputes/{id}/statusStatus to be updated in the dispute
Yapstone::DisputesApiupdate_workflow_statusPATCH /disputes/{id}/disputeWorkflowWorkflow status to be updated in Dispute
Yapstone::EvidencesApicreate_filePOST /evidences/{id}/filesUpdate a dispute evidences
Yapstone::EvidencesApicreate_textPOST /evidences/{id}/textUpdate a dispute evidences
Yapstone::EvidencesApidelete_fileDELETE /files/{id}Get the evidence by it's id
Yapstone::EvidencesApidelete_textDELETE /text/{id}Get the evidence by it's id
Yapstone::EvidencesApiget_evidenceGET /evidences/{id}Get the evidence by it's id
Yapstone::EvidencesApiget_file_content_by_idGET /files/{id}/contentGet file content by file evidence id

Documentation for Models

Documentation for Authorization

Bearer

  • Type: API key
  • API key parameter name: Authorization
  • Location: HTTP header

FAQs

Package last updated on 19 Jul 2019

Did you know?

Socket

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install

Related posts