Credentials

Splice uses your own credentials to connect to third-party logistics systems on your behalf. This ensures you maintain full control over your data and API access while enabling Splice to automate workflows across your supply chain.

How Credentials Work

When you connect a logistics provider (like FedEx, Hapag-Lloyd, or APM Terminals) to Splice:

1. You provide your credentials - API keys, usernames, passwords, or OAuth tokens from your existing accounts
2. Splice stores them securely - Credentials are encrypted and stored in our secure credential vault
3. Splice makes calls on your behalf - All API requests to subscriber systems use your credentials, not Splice's
4. You retain full control - You can update or revoke credentials at any time

Security & Privacy

• Your data stays yours - Splice never uses shared or pooled credentials
• Encrypted storage - All credentials are encrypted at rest and in transit
• Least privilege access - Splice only requests the minimum permissions needed for your workflows
• Audit trail - All API calls made with your credentials are logged for transparency

Credential Types

Splice supports various authentication methods depending on the logistics provider:

• API Keys - For services like tracking APIs and freight rate engines
• OAuth 2.0 - For modern cloud-based logistics platforms
• Username/Password - For legacy systems and portal access
• Certificate-based - For secure B2B integrations
• Custom tokens - For proprietary logistics system APIs

Managing Credentials

Adding Credentials

1. Navigate to the Credentials section in your Splice dashboard
2. Select the logistics platform you want to connect
3. Enter your existing credentials for that provider
4. Test the connection to verify access
5. Save and start using in your workflows

Updating Credentials

• Credentials can be updated at any time without breaking existing workflows
• Splice will automatically use updated credentials for new API calls

Revoking Access

• Remove credentials from Splice to immediately stop all API calls to that provider
• Existing workflow data remains intact, but new data collection stops
• You can re-add credentials later to resume automation

Best Practices

• Use dedicated API accounts when possible for better tracking and security
• Rotate credentials regularly according to your security policies
• Review permissions to ensure Splice only has access to necessary data

Troubleshooting

If you encounter credential issues:

1. Check expiration dates - Many logistics APIs have time-limited tokens
2. Verify permissions - Ensure your account has access to the required APIs
3. Test directly - Try using your credentials directly with the provider's API
4. Contact support - Splice support can help diagnose connection issues without accessing your credentials