Service Level Agreement
Monthly uptime commitment, service credits, exclusions and support acknowledgement targets.
Products
Enterprise
Volume pricing, an annual contract with invoice billing, a signed MSA and DPA, and a 99.5% monthly uptime SLA with service credits. You deal directly with the engineers who run the service.
Enterprise at a glance
What a contract includes
Everything here exists today. If you need something that is not listed, ask and we will say yes or no plainly.
Per-request pricing agreed against your expected monthly volume. Contracts start from 200,000 requests a month.
You are invoiced instead of paying by card. A purchase order and payment terms can be agreed in the contract.
A master services agreement and a data processing agreement based on public standard templates. Your legal team can read the standard versions before any call.
Legal documents99.5% uptime per calendar month. Below that, service credits apply to the month's fee. Support acknowledgement targets are set by severity.
Read the SLAA licence to redistribute SkyLink data inside your own product. The scope is written into the contract.
Batch exports or endpoints built for your integration, by agreement. We say up front whether it is something we can build.
SkyLink is a team of two. The people who answer your email are the people who build and run the service.
Documented response contracts. The current version is v3.1; earlier versions stay available as legacy versions, and changes ship as a new version.
API referenceHow an engagement works
Five steps, handled by the same two people throughout.
Step 01
Send the form on this page or write to us. Tell us which data you need, the volume you expect and any contract or security requirements.
Step 02
A call with the engineers who run the service to confirm endpoints, volume, rate limits, licensing scope and any custom work.
Step 03
We send pricing and an order form setting out volume, term, fees and any custom exports or endpoints.
Step 04
You sign the master services agreement and the data processing agreement. Both are public, so your legal team can review them first.
Step 05
Access is set up under the contract, and your questions go directly to the two engineers who run the service.
Procurement pack
The contract documents are public and can be downloaded as PDF. The MSA and DPA are based on public standard templates and are completed with your details on signature.
Monthly uptime commitment, service credits, exclusions and support acknowledgement targets.
The master agreement for Enterprise customers, completed with your details on signature.
How personal data is processed on your behalf, completed with your details on signature.
On request
The source, method, refresh cadence and licence of each dataset. Confidential, sent to evaluating buyers on request.
Every document in one place: legal documents and the trust center.
Security review
Where something is not in place, it is said plainly rather than left for a questionnaire to discover.
Transport, authentication, what the API stores about customers, webhook delivery rules and hosting, written from the system as it is today.
Read the security overviewSecurity questionnaires are answered on request, by the people who run the system.
hello [at] skylinkapi [dot] com
The Privacy Policy states where the servers are hosted and lists every sub-processor with its role and location.
Privacy Policy, section 5A published reporting route and a security.txt file, with an acknowledgement target of 3 business days.
How to reportRoadmapNot available today: single sign-on (SSO and SAML), a SOC 2 audit, data residency options, signed webhooks. If one of these is a requirement for you, tell us and we will say plainly where it stands.
Contact sales
A few details about your volume and requirements. We reply by email on business days and arrange a scoping call.
FAQ
Not answered here? Contact sales or write to hello [at] skylinkapi [dot] com.
When you need a signed contract, invoice billing, a contractual uptime commitment, white-label licensing, or more than 200,000 requests a month. Below that, the self-serve plans are the quicker route.
Pricing depends on your monthly request volume and the endpoints you use, and starts from 200,000 requests a month. We send a proposal and order form after a scoping call. Contracts are annual and billed by invoice.
We reply by email on business days and arrange a scoping call with the engineers who run the service. After that we send a proposal and an order form; the MSA and DPA are signed alongside it, and onboarding follows with the same engineers.
Yes. Enterprise includes white-label licensing. The scope depends on how and where you intend to display the data, and it is written into the contract. Some upstream data has its own licence terms, which we will tell you about before you sign.
Support is by email. It is answered by the two people who build and run the service, 08:00 to 20:00 CET, Monday to Friday. Severity 1 incidents are acknowledged within 4 support hours. Support is not staffed outside those hours, and there is no named account manager.
Yes. We answer security questionnaires, sign a data processing agreement and a master services agreement, and describe our practices at /security/. What is not in place yet is listed openly on that page.
Yes. The Data Provenance Sheet documents the source, method and licence of each dataset. It is confidential and sent to evaluating buyers on request, sometimes after a confidentiality agreement.