API Reference v2

Welcome to the API Reference v2

This documentation provides comprehensive details on how to integrate with our services using the version 2 of our API. You'll find information on authentication, available endpoints, request and response formats, and usage examples.

Our API is RESTful and uses standard HTTP methods such as GET, POST, PUT, DELETE. All requests and responses are in JSON format. For security, all API requests must be authenticated.

This version introduces several improvements, including enhanced rate limiting, new endpoints for advanced features, and more granular error reporting. Please migrate from older versions at your earliest convenience.

Core APIs

Authentication

Accessing protected resources requires authentication. We support OAuth 2.0. Obtain an access token by following the standard OAuth 2.0 flows.

POST /oauth/token

Request Body

{
  "grant_type": "client_credentials",
  "client_id": "YOUR_CLIENT_ID",
  "client_secret": "YOUR_CLIENT_SECRET"
}

Response (Success)

{
  "access_token": "eyJhbGciOiJIUzI1NiIsIn...",
  "token_type": "Bearer",
  "expires_in": 3600
}
Your access token should be included in the Authorization header of subsequent requests: Authorization: Bearer YOUR_ACCESS_TOKEN.

Users API

GET /v2/users

Retrieves a list of users.

Parameters
Name Type Description Required
limit integer Maximum number of users to return. No
offset integer Number of users to skip before starting to collect the result set. No
status string Filter users by status (e.g., 'active', 'inactive'). No

Response (Success)

[
  {
    "id": "user_123",
    "username": "alice",
    "email": "alice@example.com",
    "status": "active",
    "created_at": "2023-10-27T10:00:00Z"
  },
  {
    "id": "user_456",
    "username": "bob",
    "email": "bob@example.com",
    "status": "active",
    "created_at": "2023-10-27T10:05:00Z"
  }
]

GET /v2/users/{id}

Retrieves a specific user by their ID.

Path Parameters
Name Type Description Required
id string The unique identifier of the user. Yes

Response (Success)

{
  "id": "user_123",
  "username": "alice",
  "email": "alice@example.com",
  "status": "active",
  "created_at": "2023-10-27T10:00:00Z",
  "profile": {
    "first_name": "Alice",
    "last_name": "Smith"
  }
}

Products API

Manage product catalog, inventory, and pricing.

GET /v2/products

Retrieves a list of products.

POST /v2/products

Creates a new product.

GET /v2/products/{id}

Retrieves a specific product by ID.

PUT /v2/products/{id}

Updates an existing product.

DELETE /v2/products/{id}

Deletes a product.

Orders API

View and manage customer orders.

GET /v2/orders

Retrieves a list of orders.

POST /v2/orders

Creates a new order.

GET /v2/orders/{id}

Retrieves a specific order by ID.

Advanced Features

Explore our advanced features to enhance your integration.

Notifications API

Send real-time notifications to users.

POST /v2/notifications

Sends a notification.

{
  "user_id": "user_123",
  "message": "Your order has been shipped!",
  "type": "email", // or "sms", "push"
  "priority": "high"
}

Reporting API

Generate custom reports on sales, user activity, and more.

GET /v2/reports

Retrieves available report types.

POST /v2/reports/generate

Initiates the generation of a report.

Integrations API

Manage third-party integrations.

GET /v2/integrations

Lists available integrations.

Changelog

Stay up-to-date with the latest changes to our API.

v2.1.0 (October 26, 2023)

  • Added new /v2/products/search endpoint.
  • Improved error codes for better debugging.
  • Fixed bug in order status updates.

v2.0.0 (September 15, 2023)

  • Initial release of API v2.
  • Introduced new authentication flow.
  • Added advanced features like Notifications and Reporting APIs.

Getting Started

Ready to integrate? Follow these steps:

  1. Obtain your API credentials (Client ID and Client Secret) from your developer dashboard.
  2. Use the /oauth/token endpoint to get an access token.
  3. Make requests to the desired API endpoints, including the access token in the Authorization header.
  4. Consult the detailed endpoint documentation above for specific usage.
For any issues or questions, please visit our Support Portal.