LoadLoom API and Webhooks Agreement

This API and Webhooks Agreement (the "Agreement") is between you and SHIPVISTA CORPORATION, operating the LoadLoom platform, U9, 9 Royalcrest Rd, Etobicoke, ON M9V 2L6 ("LoadLoom", "we", "us"). It applies the moment you create an API key, call any LoadLoom API endpoint, or register a webhook endpoint, whether you do so as a customer, a channel partner, a carrier, or a developer acting for any of them.

If you use the API on behalf of a company, you represent that you have authority to bind that company, and "you" means that company. This Agreement adds to, and does not replace, the LoadLoom Terms of Use and any service terms that govern the underlying shipments (including the Container Shipping Terms and, for channel partners, the Channel Partner Agreement). If those documents conflict with this one about a shipment, they win; about the API itself, this Agreement wins.

We grant you a limited, revocable, non-exclusive, non-transferable licence to call the LoadLoom API and receive webhooks, only for your own shipping operations or for an application that serves your own customers, and only in accordance with this Agreement and our documentation at loadloom.com/developers/api.

No other rights are granted. You may not sell, rent, sublicense or share access to the API itself; resell our data as a product; use the API to build or train a competing rate, pricing or carrier database; or present LoadLoom quotes as your own system's output without identifying LoadLoom where our brand terms require it.

An "application" includes an AI agent or assistant you connect through our API or MCP server. Agents act on your behalf with your key: you remain responsible for everything they do, their calls count against your limits, and information returned to them is the same operational information with the same disclaimers, including that estimates remain estimates. Agents cannot sign, pay, or create accounts; those remain human acts on our platform.

API keys belong to the account that created them and must be kept secret. You are responsible for every call made with your keys, whether or not you authorized it, until you revoke the key from your Developers page. Store keys server-side only; never embed a secret key in a browser, mobile app, or public repository.

Webhook signing secrets are shown once at creation. You must verify the signature header on every webhook delivery before trusting its contents; deliveries that fail your verification should be rejected. If you believe a key or secret is compromised, revoke it immediately and create a new one. Tell us at security@loadloom.com if you suspect a breach that could affect other users.

You must not use the API to break the law, infringe rights, send spam, probe or degrade our systems, evade our anti-abuse controls, misrepresent shipment facts, or create accounts by machine. Account creation is a human act on our website; the API does not create accounts, and attempting to automate signup is a violation of this Agreement.

Rate limits protect everyone. The current default is 120 requests per hour per key, and specific endpoints may carry their own limits as documented. We may change limits with notice on the documentation page. Sustained attempts to evade limits (key cycling, request spreading, header forgery) are grounds for immediate suspension.

A quote returned by the API is an offer on the same terms as a quote on our website, including its PriceLock window. A booking made through the API forms the same contract as a booking made on the website, governed by the service terms for that mode. The API is a doorway, never a different deal.

Prices returned by the API are Direct-Pay (bank transfer) prices unless marked otherwise, exactly as on the site. Where tax applies, the API returns it per the same place-of-supply rules the website uses. You are responsible for displaying prices accurately to your own customers, including any margin you add under a channel partner arrangement.

Webhooks are notifications, not the system of record. We attempt delivery promptly, retry failed deliveries with backoff, and pause an endpoint after twenty consecutive failures, with an email to you. We do not guarantee delivery, ordering, or exactly-once semantics; your integration must tolerate duplicates and gaps and should reconcile against the API when accuracy matters.

Your endpoint must be a public HTTPS URL that you control. You must not point webhooks at infrastructure you do not have authority over. Payloads may contain shipment data belonging to your account; protect them accordingly.

Data you submit through the API (shipment details, addresses, order data) remains yours. You grant us the licence needed to process it for providing the services, the same as when you type it into the website, and our Privacy Policy governs personal information within it. You are responsible for having the right to submit any personal information you send us, including your own customers' details.

Data we return (quotes, tracking events, documents, directory facts) is provided for your use in the shipment at hand and your own records and applications. You may cache it for operational purposes, but you may not assemble our responses into a dataset for resale, for benchmarking publications, or for training pricing systems that compete with LoadLoom.

Some API responses carry information that originates with third parties: ocean carriers, rail and road carriers, terminal operators, government registries such as the FMCSA, and mapping providers. That information passes through as received. The originating party owns it, and their terms may apply to your further use of it.

We do not warrant third-party data, and schedule, position and status information in particular can change without notice. Sailing schedules move, terminals reorder work, and registries lag reality. Build your operations on the shipment documents and confirmations, not on passthrough telemetry alone.

The API is currently provided without a separate fee; you pay only for the shipments and services you book, under their own terms. If we introduce API fees or paid tiers, we will give at least thirty days notice on the documentation page and by email to affected key holders, and continued use after the effective date is acceptance.

The version lives in the path (currently /api/v1/). Within a version we make only additive changes: new fields and endpoints may appear, and existing fields do not change meaning or disappear. Anything breaking becomes a new version.

When we retire a version we will give at least ninety days notice by email to active key holders and on the documentation page, except where an immediate change is required by law or to close a security hole. Webhook event payloads follow the same additive discipline.

We run the API on the same infrastructure as the platform and publish component status at loadloom.com/status. The API is provided without an uptime guarantee or service level agreement unless you have signed a separate agreement with us that provides one. Support is available through the same channels as the platform, and the delivery log on your Developers page is the first place to look for webhook questions.

You may stop using the API at any time and revoke your keys from your Developers page. We may suspend or revoke keys, pause webhooks, or terminate this Agreement immediately where we reasonably believe there is abuse, a security risk, a legal requirement, unpaid amounts on the account, or a breach of this Agreement; otherwise we will give reasonable notice. Suspension of the API does not by itself cancel shipments already booked, which continue under their own terms.

On termination your licence ends, keys stop working, and you must delete cached API data that this Agreement does not entitle you to keep, except records you need for legal, accounting or dispute purposes.

The API, its documentation, schemas, and the LoadLoom platform remain our property and that of our licensors. Nothing here transfers ownership to you, and nothing transfers your application or your data to us. If you send us feedback or suggestions about the API, we may use them without restriction or payment, and you confirm you are entitled to share them.

The API and webhooks are provided as is and as available. To the fullest extent the law allows, we disclaim all warranties, express or implied, including merchantability, fitness for a particular purpose, and non-infringement, and we do not warrant that the API will be uninterrupted, error-free, or that data will be current at the moment you read it. Some jurisdictions do not allow certain disclaimers, so parts of this section may not apply to you; consumer protections that cannot be waived are not waived.

Our total liability arising from the API or webhooks in any twelve-month period is capped at the greater of the API fees you paid us in that period and one hundred Canadian dollars. We are not liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, revenue, data or goodwill, even if advised of the possibility. Liability for a shipment itself is governed by that shipment's service terms, not this cap. Nothing limits liability that cannot be limited by law, including for fraud or willful misconduct.

You will defend and indemnify us against third-party claims arising from your application, your use of the API in breach of this Agreement, your data, or your dealings with your own customers, including reasonable legal costs, provided we notify you promptly and let you control the defence with our reasonable cooperation.

This Agreement is governed by the laws of Ontario and the federal laws of Canada applicable there. Disputes with persons in the United States are resolved by binding individual arbitration administered by the American Arbitration Association (single arbitrator, videoconference available, Federal Arbitration Act governs), with a small-claims carve-out and a waiver of class and representative proceedings; for everyone else the courts of Ontario have exclusive jurisdiction. Twenty-five or more coordinated demands presenting similar claims are administered in sequential batches under the AAA's Mass Arbitration Supplementary Rules, remaining demands stayed with limitation periods tolled; and a person subject to the arbitration paragraph may opt out of it and the class waiver within thirty days of first accepting this Agreement by written notice to legal@loadloom.com. Consumers keep every non-waivable right of their home jurisdiction, and the arbitration paragraph and class waiver do not apply to consumers resident in Quebec. We may update this Agreement by posting the new version here with a new effective date; material changes get thirty days notice to active key holders, and continued use after the effective date is acceptance.

You may not assign this Agreement without our consent; we may assign it within our corporate group or in a merger or sale. If part of this Agreement is unenforceable, the rest stands. This Agreement, the documents it references, and your service terms are the entire agreement about the API. Questions: developers@loadloom.com.