FMCSA Portal Connector
Status: Planned: not built. The maker does not publish its protocol or interface; ZAITRACK builds it once it does.
| Kind | Version | Publisher | Licence |
|---|---|---|---|
| Connector | 0.1.0 | ZAITRACK | Apache-2.0 |
What it does
Planned: ZAITRACK does not connect to the FMCSA portal yet. Nothing is installed or run until it does.
- Regions: US
- Capabilities:
integration.customs.carrier.lookup,integration.customs.eld.report,integration.customs.safety.sync
How to use it
Not yet: see its status above.
Configuration
None: it needs no settings.
Credentials
Each is a secret setting of the installation: kept sealed (OpenBao in production), never shown again; Adapter Studio shows it as set.
fmcsa_webkeyfmcsa_carrier_id
Limits
- Memory: 256 MB
- Time per call: 30,000 ms
- Largest message: 1,048,576 bytes
- Calls at once: 16
- Network: only
portal.fmcsa.dot.gov,mobile.fmcsa.dot.gov - Its own key-value store: up to 10,000 keys of 65,536 bytes
Troubleshooting
- Credentials refused. The secret settings must be the ones the provider issued for this account and environment (sandbox or live); give them again in Adapter Studio, since they are never shown back.
- Rate limited. The provider's limit applies to the account: calls are retried with a growing pause; spread scheduled work or ask the provider for a higher limit.
- Nothing is sent or synced. The installation must be active, its version approved; it reaches only the hosts listed under Limits.
- Webhooks rejected. The webhook secret must match the one configured at the provider; a request whose signature does not match is refused.
Source
adapters/connectors/fmcsa-portal