Welcome to LDTP Support

Authentication & API Keys Generation

All requests to the LDTP infrastructure must be authenticated via an API Key or an OAuth2 Bearer token. Anonymous requests will be strictly rejected with a 401 Unauthorized status code.

Generating a new API Key:

1. Log in to your LDTP Enterprise Dashboard.
2. Navigate to Settings > Developer > API Access.
3. Click on Generate New Token.
4. Select the required scopes (e.g., read:metrics, write:config).
5. Copy the token immediately. For security reasons, it will only be displayed once.

Pass the key in your request headers like so: Authorization: Bearer YOUR_API_KEY

Migrating to v2 REST Endpoints

As announced in Q4 2025, the v1 REST endpoints are officially deprecated and will be fully decommissioned by the end of the current fiscal year. All clients must migrate to the v2 endpoints to ensure uninterrupted service.

Key Changes in v2:

• Base URL changed from api.ldtp.com/v1/ to api.ldtp.com/v2/.
• Rate limits are now strictly enforced at 500 requests per minute per IP address.
• Payloads for POST requests must now explicitly include "Content-Type": "application/json".

If you experience a 429 Too Many Requests error, ensure you are properly implementing exponential backoff in your retry logic.

Billing, Invoices, and Subscription FAQ

Our automated billing system issues invoices on the 1st of every calendar month. You can download PDF copies of your past invoices directly from the Billing portal.

Payment Methods Accepted:

We accept major credit cards (Visa, MasterCard, Amex), SEPA Direct Debit (for EU clients), and International Wire Transfers (for Net-30 Enterprise clients only).

Why was my card declined?

If your card was declined, please verify that your bank does not block international cross-border transactions. LDTP Systems is registered in the European Union, so US-based corporate cards may require pre-authorization for EU charges.

Troubleshooting Connection Timeouts (Error 522)

An Error 522 indicates that our edge network was unable to establish a TCP connection to your origin server. This is almost always caused by a firewall configuration issue on your end.

Steps to resolve:

• Check that your origin server is actively listening on port 80 or 443.
• Review your server's iptables or firewall rules (e.g., UFW). Ensure that you are not dropping packets from LDTP's IP ranges.
• If you are using a hosting provider like AWS or Google Cloud, verify that your Security Groups or VPC firewall rules allow inbound traffic from the internet to your web ports.
• Check your web server logs (e.g., /var/log/nginx/error.log) to see if requests are reaching your server but being dropped due to application-level timeouts.