From Test Key to Production: Preparing Your QUOTC Integration

Connecting a data source involves more than receiving the first successful response. Your application needs to interpret records correctly, handle interruptions and keep credentials secure. The QUOTC test period gives you time to check these details before requesting production access.

Start with a test key

Create a QUOTC account and open My keys in your dashboard. When creating a test key, enter the IP address of the server that will connect to the API.

The free test key provides access to EUR/USD for 30 days from creation. Prepare your server beforehand so you can use that period effectively.

Choose the server IP carefully. You cannot edit it yourself after creating the key; changes must be requested through support.

Verify how your application reads the data

Use the API documentation as your integration reference. An example shown on a product page illustrates the data structure but does not replace the technical specification.

Check how your application interprets timestamps, price fields and any additional values. Confirm that records are processed in the correct order and that your charts display the intended intervals.

QUOTC quotations are algorithmically generated. They are not official exchange prices and do not reflect actual market conditions. Make this distinction clear wherever your application displays the data.

Test interruptions and access restrictions

A connection that works under normal conditions still needs predictable behaviour when something changes.

Before moving to production, check that your application:

• Handles connection failures without uncontrolled retries.

• Distinguishes unavailable data from an unchanged price.

• Detects unexpected or incomplete responses.

• Stops relying on a key when access expires or is disabled.

• Keeps API credentials out of public pages, screenshots and application logs.

Your users should be able to distinguish a technical interruption from a valid update. Avoid silently presenting an old record as newly received data.

Keep credentials on your server

QUOTC keys are linked to a server IP. Plan your integration so requests originate from the authorised server rather than directly from visitors’ browsers.

The dashboard displays only the first and last three characters of a key. Use Copy key to obtain its full value, then store it in your server configuration with appropriate access controls.

When contacting support, identify the key using its mask and server IP. Do not paste the full credential into a ticket.

Create a production key

Once your integration is ready, create a production key in the dashboard and enter its server IP.

Creating a production key does not activate access. Contact support to arrange payment and activation. Production access costs 500 USD per month per key and covers all 28 listed currency pairs.

Each production key has its own status and access period. Check the activation and expiry details in your dashboard before switching your application to the new key.

Make the transition deliberately

Update your server configuration, verify the production connection and confirm that your application handles the additional currency pairs correctly.

Keep the same checks you used during testing: validate incoming records, monitor connection errors and display the generated nature of the quotations clearly. A controlled transition makes the integration easier to maintain and problems easier to diagnose.