About Dispute API 3.0

👍

Availability

Dispute API 3.0 is still under development. The information in this reference is subject to change as development proceeds and is not a guarantee of future functionality. If you are interested in using this API, contact Galileo for details.

• Galileo's Dispute API 3.0 provides a robust set of endpoints to create dispute claims and manage them through the entire dispute process.
• Dispute API 3.0 is a RESTful-style API. All verbs are POST.
• The endpoint names are the /paths in the Open API spec file that forms the basis for this reference.

For instructions on using these endpoints, consult these guides:

• Creating an API 3.0 Dispute — How to follow the flow-intake sequence to create a dispute.
• Dispute API 3.0 Workflows — Sequence of endpoints to use for each dispute type.
• Managing API 3.0 Disputes — What to do with disputes after they have been created.

Base URL

For this API use the tenanted URL that Galileo assigns you: https://{corename}.gft-dispute-api.{env}.gpsrv.com/gft-dispute-api/1.0/endpointpath where

• corename is the name of your core, as assigned by Galileo.
• env is the environment: cv for client validation and pd for production.

Authentication

You must obtain API login credentials from Galileo. If you already have credentials for Program API, you can use those. Unlike the Program API and some other APIs, you pass your credentials in the request header as Authorization: Basic {token}, where {token} is base64-encoded apilogin:transkey.

Cases

📘

Note

Most of the request and response field names are in PascalCase, but a few are in camelCase. This is intended. Make sure you follow the same case conventions as shown in the reference.