Get started

Using the playground

Test with your account or a key.

What the tester sends

Use my account

Signed in, the playground gets a token for your own account that lasts 15 minutes, and sends it as Authorization: Bearer. It works on every plan with no signing. Its requests count against your account's monthly requests and limits, including your plan's per-minute limit. It can only read, so submitting or cancelling a job cannot be tried here: send those from your server, with a signed request.

Memory-only key

Or paste a Free or Starter key. It stays in this page's memory and is cleared when the page closes.

Direct request

The browser calls https://ir.railcore.tech. RailCore docs do not proxy or record the key or the token.

20 second guard

Long requests can be cancelled and are stopped automatically after the playground timeout.

Endpoint examples

Every endpoint page has cURL, Node.js, Python, PHP, Go and Java samples that read the key from an environment variable.

Workflow

  1. 1Choose an endpoint from the API reference.
  2. 2Signed in, choose Use my account: it works on every plan. Or paste a Free or Starter key with the required scope. A pasted Growth, Scale or Enterprise key is refused, because those keys must sign every request.
  3. 3Review the populated path, query, or JSON body fields. Clear optional fields you do not want to send.
  4. 4Send the request. Inspect the HTTP status, measured browser latency, body, and exposed response headers.
  5. 5Use the endpoint page's code examples when moving the tested request into your server-side application.

Never enter a signing secret here

The playground never asks for one. Keep it on your server and sign there with the HMAC examples. To try a Growth, Scale and Enterprise plan from this page, sign in and choose Use my account.

CORS and exposed headers

If a browser blocks the request, use the generated server-side sample. Browsers show only headers that the API exposes through CORS.

Last updated