Becoming a provider
How Localoy registers your company as a Technology Provider — sandbox keys, a test partner, review, production keys and listing — and what a suspension means.
Localoy registers Technology Providers itself. There is no sign-up form: you work with Localoy's partnerships team from the first conversation until you go live.
- Your team → Localoy: Ask to become a provider
- Localoy → Localoy: Register you: modules, scopes
- Localoy → Your team: Sandbox key + test partner
- Your team → Your team: Build and test in the sandbox
- Your team → Localoy: Ask for a review
- Localoy → Your team: Production key
- — If Localoy lists you —
- Localoy → Partners: Shown in the provider list
- Partners → Your team: Connect with a code
1. Contact Localoy#
Reach Localoy through your Localoy partnerships contact. Be ready to explain what your platform does, which of its customers use Localoy, which modules you serve and which scopes you need — and why you need any scope that shares customers' personal data.
2. What Localoy registers#
| Field | Detail | Partners see it |
|---|---|---|
| Name | Your product's name. | Yes |
| Provider key | Your permanent identifier. It is part of your deep link and GET /ping returns it. It cannot be changed. | In the link |
| Mark and logo | A mark of 1–3 characters, and a logo image. | Yes |
| Category | POS, Ticketing, Restaurant, ERP, Website Builder, Hotel or Others. | Yes |
| Description | 20–500 characters on what your integration does for a partner. | Yes |
| Website | An https address. | Yes |
| Support email | Where partners reach you about the integration. | Yes |
| Modules | Any of Events, Dining and Activities. See Modules. | Yes |
| Allowed scopes | The scopes you may ask partners for. | As the choices they tick |
| Listed | Whether you appear in the list partners browse. | — |
Localoy can change any of these later, except the provider key. Narrowing your modules or your allowed scopes applies to every connection from the next call. Widening them grants nothing by itself: each partner decides whether to give you a new scope.
3. Build in the sandbox#
Localoy issues you a sandbox key, starting ltp_sbx_, and a test partner account: a partner
account you can sign in to, so that you can play the partner's part — generate codes, change your
scopes, pause you and disconnect you.
A key is shown once, when Localoy issues it, and Localoy keeps only a hash of it. Store yours in a secret manager straight away. A lost key cannot be recovered; ask for a new one.
Follow the Quickstart, then build the rest of your integration with Sandbox and production at hand.
4. Review and production keys#
When your integration works end to end in the sandbox, work through the
go-live checklist and ask your partnerships contact for a review. After it,
Localoy issues your production key, starting ltp_live_.
You can hold up to 5 live keys in each environment — enough to give each of your systems its own key, and to replace a key without downtime.
5. Listing#
Localoy decides whether to list you. A listed provider appears to every partner on the Partner Portal's Open Network → Technology Providers page. An unlisted provider does not appear there, but its deep link still works — useful while you connect your first partners.
Listing is not an endorsement
Localoy does not certify Technology Providers, and a listing does not vouch for your product. It means partners can find you. What each partner grants you is its own decision, and it can end the connection at any time.
Suspension#
Localoy can suspend a Technology Provider, and records its reason when it does. While you are suspended:
| Area | Effect |
|---|---|
| Your keys | Every call with any of your keys answers 403 provider_suspended. |
| Webhooks | Nothing is delivered to your endpoints. |
| Partners | You leave the provider list, and your deep link stops working. Partners already connected to you see you as suspended by Localoy. |
| Connections | Every connection is kept. When Localoy resumes you, each one is restored as it was. |
Talk to your partnerships contact to resolve a suspension.