LogoLogo
System status
Commerce API references
Commerce API references
  • Commerce API references
  • Warnings and error codes
    • Errors
    • Error codes
      • HTTP response status codes
      • Error format for Shopper APIs
      • Error codes for Shopper APIs
        • 400 Bad Request
        • 401 Unauthorized
        • 403 Forbidden
        • 404 Not Found
        • 405 Method Not Allowed
        • 409 Conflict
        • 412 Precondition Failed
        • 413 Payload Too Large
        • 500 Internal Server Error
      • Error format for Admin APIs
        • Async error objects
        • Sync error objects
        • Deployment objects
        • Warning objects
      • Error codes for Admin APIs
        • Error patterns
        • Supported image types
        • Asynchronous response error codes
        • Deployment error codes
        • Synchronous response error codes
  • Commerce API reference guide
    • API structure
      • API keys
      • Supported OAuth and Commerce API formats
      • Mini cart widget
      • Custom attributes
      • Fields used as keys
      • Fields and expand query parameters
      • Caching responses
      • CORS support
      • JSONP support
      • Transport
      • Service profiles
      • Supported protocols and formats
      • Elements
      • Rate limiting
      • Locale and currency
      • Exchange rate
      • Product identifier
      • Product external reference identifier (ERID)
      • Customer external reference identifier ERID
      • Cancel request process
      • Failover and redundancy
      • Troubleshooting API calls
    • Shopper APIs reference
      • Carts
        • Offers
          • Offer types
          • POP offers
          • Applied offers
          • Eligible offers
      • Orders
      • Returns
      • Links
    • Admin APIs reference
      • Subscriptions
      • Sites
      • Products
      • Live changes
      • Authorized shipping and billing countries
      • Merchandising
      • Disclosures
    • Glossary
Powered by GitBook
On this page
  • Accept header format for OAuth
  • Accept header format for Commerce API
  • Query parameter format
  • Supported webhook formats
  1. Commerce API reference guide
  2. API structure

Supported OAuth and Commerce API formats

Learn about supported OAuth and Commerce API formats.

PreviousAPI keysNextMini cart widget

Last updated 4 months ago

The Commerce API and OAuth support requests and responses in XML and JSON formats. XML is the default for the Commerce API; JSON is the default for the OAuth API. You can override the default in the Accept header for both the OAuth and Commerce API. You can also override the default format using the format query parameter in the Commerce API.

Accept header format for OAuth

The following example shows the supported accept header format for the resource.

Accept: application/json (default)
Accept: application/xml

Accept header format for Commerce API

The following example shows the supported accept header format for resource.

Accept: application/xml (default)
Accept: application/json

Query parameter format

The following GET request sets the parameter format to JSON:

GET /shoppers/me/categories?format=json
Accept: */*
Authorization: bearer your_access_token

Supported webhook formats

Digital River supports the XML format for webhooks.

OAuth
Shoppers