Line Me Up
Customers
Start free
Developers
Contents
On this page

Reference

Support and status

Help when an integration is not doing what you expect.

Asking for help#

Write to us from the contact page. Say it is about the API, and include what lets us find the request quickly:

  • the business's name, and the key's name as Settings shows it — never the key;
  • the endpoint and method, and when you called it, with the time zone;
  • the status and the error body you got back;
  • for a webhook, the LineMeUp-Delivery-Id or the event's id.

Never send us a key or a signing secret, and never paste one into a ticket or a chat. We do not need it, and nobody from Line Me Up will ask for it. If one has been shared, revoke the key or roll the secret in Settings → Integrations.

Before writing, two places answer most questions:

  • Errors — every code, what it means and how to fix it.
  • The endpoint's delivery log in Settings — every attempt, what your receiver answered, and the request exactly as sent.

Service status#

The API's health check is public and needs no key. It answers 200 while the API is up: 

curl -i https://business.linemeup.in/api/health
# HTTP/1.1 200 OK — the API is up

If it answers and your calls still fail with a 5xx for more than a few minutes, tell us, with the times. Webhooks are not lost while we recover: every delivery waits and is retried on the schedule on Webhooks.

Changes to the API itself — new endpoints, fields and events — are dated on Versioning and changelog.

Reporting a security problem#

If you find a way to read or change a business's data without its key, or a key reaching past its scopes, lines or desks, tell us through the contact page and start the message with Security. Describe what you did and what you saw; do not include another business's data, and do not test against a business that is not yours.

Every report is read by the people who build the API. If a key or a secret of yours may have been exposed while you looked, revoke or roll it straight away.