CDNX Customer API Documentation

Overview

The CDNX Customer API provides programmatic access to add/edit and remove data from CDNX's bid, ask and auction price realized data sets.

Before you can start using the CDNX Customer API, you'll need to complete the following steps:

To obtain API credentials, please contact api@greysheet.com

Before going live with your integration:

Use the development environment for testing: https://cdnxapidev.greysheet.com/api
Access the interactive API sandbox at: https://cdnxapidev.greysheet.com/swagger
Test all required endpoints before moving to production

Once testing is complete:

Update your application to use the production endpoint: https://cdnxapi.greysheet.com/api
Use your production API credentials (not the sandbox token)
Monitor your usage and ensure proper error handling

The CDNX Customer API is a RESTful API with endpoints located at:

All API calls require the following authentication headers to be passed:

Postman Headers Example:

Interactive API documentation and testing is available via Swagger:

https://cdnxapidev.greysheet.com/swagger
To test the API calls, click the Authorize button and enter your api key and token. Click authorize on each of them and then you can click close
Example endpoint to get your bids and asks: https://cdnxapidev.greysheet.com/api/GetMyBidAsk

Postman API Call Example:

Many of the calls in the previous version of the Api will continue to work without modification. Here is a list of the major changes:

Asks: The previous system of asks has been deprecated. Asks now represent actual items in your inventory for sale or in auction. The main difference is that the quantity will always be 1, and listing multiple items with the same Pcgs Number/Gsid, grade and grading service will be possible when the pricing are different. In the previous system, all items had to have the same price.
cdn_entry_id: cdn_entry_id has been replaced by Gsid throughout the Api. This is to make the data more consistent with the rest of the CDN Exchange website.
id: Previously id was either supplied by you or was the index of the item within the array of items passed to the api. This was used to allow identification of rows that had errors. In the new system, all inserts will return the id of that record in our database. This id will be needed when doing update and delete operations. The previous id has been renamed to internal_id and internal_id will server the same purpose as the previous id value. When doing an insert an array of internal_id and id will be returned so you can match the records.
APR data: This version of the API also allows you to add/edit/remove APR data. These operation are performed on a single record at a time, not in batches like the bid and ask calls.