Integration manual
Regional endpoints
One integration contract. Three explicit storage endpoints.
Enable the regions you need
European Union: https://eu.mimeprotect.com. United States: https://us.mimeprotect.com. FedRAMP storage jurisdiction: https://fedramp.mimeprotect.com. Enable each regional workspace in your account, then create a key in that region. Your key must match the selected endpoint. API keys are looked up in the selected regional store.
What the endpoint controls
The hostname selects the jurisdiction-restricted KV namespace for retained verification records. Authoritative Durable Objects use the matching jurisdiction subnamespace. Hostname selection cannot be overridden with a request body region field or arbitrary header.
What to agree separately
Storage jurisdiction is distinct from request processing, cache locations, logging and external providers. Agree the complete data flow and operational controls for your workload. The fedramp storage endpoint is not a claim that MimeProtect is FedRAMP authorised.
Outages and migration
Missing regional storage returns a configuration error. Requests never silently fail over into a different region. Region migration requires an explicit service operation; changing an endpoint does not move existing documents, keys or subscriptions.
Ready to connect it?
Open your regional workspace, create a sandbox key and test the complete flow with synthetic data. Keep the returned identifiers and inspect every result before moving to production.
Open the sandbox →Discuss your requirements →