TEOS User Guides
White Label Portal
White Label Portal
  • 👋Welcome!
  • Admin user guide
    • Portal configuration
      • Admin users management
      • Tenant configuration
      • Branding management
      • Asset configuration
      • Features configuration
        • Purchase assets and Featured asset
          • Collection methods configuration
          • Payment methods configuration
          • Templates for purchase details and invoice details
        • Redemption functionality
          • Template for redemption details
        • KYC checks
      • Reference Code Logic
      • How to get API keys of third party services
      • How to prepare custom HTML
    • Admin functionality
  • How your users interact with the portal
  • Partner Onboarding
    • Payrexx
    • Coinify
    • Shufti
  • WLP versions and changelog
    • Version 1.3
    • Version 1.2
    • Version 1.1
    • Version 1.0
    • Version 0.18
    • Version 0.17
    • Version 0.16
    • Earlier versions
  • ⁉️Troubleshooting
  • Glossary
  • WLP API documentation
Powered by GitBook
On this page
  • Versioning
  • Paging
  • Endpoints
  • Best Practices

Was this helpful?

Edit on GitHub

WLP API documentation

Welcome to the WLP API documentation. This API follows the OData protocol.

PreviousGlossary

Last updated 11 days ago

Was this helpful?

Introduction

The latest Swagger documentation is available at .

Versioning

The API uses an api-version query parameter to specify the version of the request. If no version is specified, the API defaults to the latest available version, which is currently 1.3.

Example:

  • Explicit versioning:

    GET /odata/Orders?api-version=1.3
  • Using the default version:

    GET /odata/Orders

    Since no api-version parameter is provided, the API will assume version 1.3 by default.

Paging

The majority of endpoints have a limit of 100 rows per response. Except for the following endpoints:

  • odata/Currencies

  • odata/Languages

  • odata/Countries

Endpoints

General Structure

Each endpoint follows OData conventions, enabling filtering, sorting, and expanding related entities.

Example Endpoints

List Orders

GET /odata/Orders?api-version=1.3

Fetch a Single Order

GET /odata/Orders(1)?api-version=1.3

Best Practices

Efficient Data Retrieval

To optimize performance:

  • Use $select to specify only the required properties.

  • Apply $filter to reduce the dataset size.

  • Use $top and $skip for paging, adhering to the 100-row limit.

  • Avoid $expand unless necessary, as it can impact performance.

Example:

GET /odata/Orders?$select=Id,Name&$filter=CreatedOn gt '2024-01-01'&api-version=1.3

Paging Implementation

Example:

GET /odata/Orders?$top=100&$skip=200&api-version=1.3
this URL