Jump to Content
Demandbase
GuidesAPI ReferenceChangelogDiscussions
DiscussionsChangelogLog InDemandbase
Guides
DiscussionsChangelogLog In
GuidesAPI ReferenceChangelogDiscussions

documentation

  • Welcome
  • Demandbase APIs
    • Getting Started with Demandbase
    • Authenticating with the APIs
    • B2B API
      • Overview
      • Authentication
      • Make Your First Request
      • Rate Limits
      • Best Practices
      • Configuring Webhooks For Subscription API
      • FAQ
      • Credit Consumption Model
      • Available Endpoints
      • IV API to B2B API Migration
    • Data Export API
      • Overview
      • Authentication
      • Make Your First Request
      • How To Use Filters
      • Rate Limits
      • Handling Errors
      • Available Endpoints
      • FAQ
      • Collections
    • Data Import API
      • Overview
      • Authentication
      • Make Your First Request
      • Rate Limits
      • CSV Record Matching And Data Mapping
      • Importing Intent Activities
      • Available Endpoints
    • User Admin API
      • Overview
      • Authentication
      • Available Endpoints
    • Credit Usage API
      • Overview
      • Authentication
      • Available Endpoints
  • MCP
    • ChatGPT
    • Claude
    • VS Code
    • Gemini
    • Copilot
      • Instructions
    • Credit Management
  • Partner Tag
Powered by 

Handling Errors

Handling Errors

Each endpoint describes possible 400 (Bad Request), 401 (Unauthorized), 403 (Forbidden), 404 (Not Found), etc. responses in the OpenAPI specification.

Example Error Response:

{
  "errorCode": "400-115",
  "errorMessage": "Invalid field names: {Account}.All, {Account}.test",
  "diagnosticCode": "ce0fc1770e0d425b88892df4f663bf07"
}

Updated 16 days ago


Rate Limits
Available Endpoints