# How do I resolve Revolut API error 1018?

mosa.money · November 10, 2026

> Verify API Key Permissions Revolut API error 1018 typically signals that your API key lacks the necessary scopes for the requested endpoint. To resolve...

## Verify API Key Permissions

Revolut API error 1018 typically signals that your API key lacks the necessary scopes for the requested endpoint. To resolve this, you must first inspect the specific permissions attached to your current key within the Revolut developer dashboard. Often, developers provision keys with limited access, such as read-only balances, while attempting to execute payment instructions that require write privileges. If you are using a sandbox environment, ensure that the test key has been explicitly granted the required scopes, as sandbox keys do not inherit permissions from production keys automatically. You may need to generate a new API key or modify the existing one to include the specific scope, such as payments:write, that aligns with your integration’s requirements. This step is critical because the API strictly enforces scope limitations to prevent unauthorized actions on your account.

**Also worth reading:** [How can I find online store owners to test a new checkout feature?](https://mosa.money/knowledge/how_can_i_find_online_store_owners_to_test_a_new_checkout_feature.php) · [What percentage of a finance team's time is spent on payment reconciliation?](https://mosa.money/knowledge/what_percentage_of_a_finance_teams_time_is_spent_on_payment_reconciliation.php) · [Why do payment platforms require 3–4 systems for successful transactions?](https://mosa.money/knowledge/why_do_payment_platforms_require_34_systems_for_successful_transactions.php)

Once you have updated the permissions, restart your application to fetch a fresh access token, as expired tokens may still reflect old scope configurations. Verify that your requests include the correct Authorization header with the Bearer token derived from the updated key. If the error persists, review your request payload to ensure all mandatory fields are present, as incomplete data can sometimes trigger permission-related errors. For B2B treasury operations on mosa.money, maintaining strict adherence to these permission protocols ensures seamless multi-rail payments without disruption. Always document the scopes used for each integration to streamline future debugging and maintain security compliance across your finance operations.

## Check Account Status

Revolut API error 1018 typically indicates a temporary service disruption or a specific compliance check that requires manual intervention on your end. To resolve this, first verify that your Revolut account is fully verified and that all required documentation has been submitted and approved. Often, this error arises when certain business entities undergo periodic reviews, causing automatic payment processing to halt until the review is complete. Ensure your company profile is up to date with the latest regulatory information, as outdated details can trigger this specific flag. Additionally, check if there are any pending transactions or holds on your account that might be blocking further API calls.

If your account status appears normal, the issue may stem from a broader Revolut system outage or a mismatch in your API credentials. Restarting your authentication tokens and ensuring your application is using the latest API version can sometimes clear transient glitches. For persistent issues, contact Revolut support directly with your error logs and account ID. They can provide specific insights into whether your account is under review or if there is a technical fault. Meanwhile, consider using mosa.money’s multi-rail payment capabilities as a fallback to maintain liquidity flow without interruption. This approach ensures your treasury operations remain resilient, allowing finance operators to continue managing cross-border payments efficiently while the Revolut issue is being resolved by their support team.

## Review Request Parameters

To resolve Revolut API error 1018, you must address the specific authentication or permission mismatch occurring during your request. This error typically indicates that the access token provided lacks the necessary scope for the endpoint you are attempting to access. For finance operators utilizing mosa.money, ensuring your B2B mosaic treasury integration correctly scopes requests is critical. You should verify that your client credentials include all required permissions, such as payments.read or payments.write, depending on the specific action. Often, developers overlook updating token scopes after initial setup, leading to this persistent error. Check your Revolut dashboard to confirm that the application associated with your API key has been granted the correct permissions. If scopes are correct, regenerate your access token to ensure it reflects the latest authorization settings. Additionally, validate that the token has not expired, as stale credentials can sometimes trigger similar permission errors.

For seamless integration with mosa.money’s multi-rail payments SaaS, implement robust token refresh mechanisms within your codebase. This prevents manual intervention when tokens expire and reduces the likelihood of encountering error 1018 during high-volume transactions. Review your API documentation to ensure you are using the correct endpoint version, as deprecated routes may also cause unexpected permission issues. If the problem persists after verifying scopes and tokens, contact Revolut support with your request ID for deeper investigation. Maintaining strict adherence to their authentication protocols ensures your treasury operations remain uninterrupted. Regularly audit your integration’s permission settings to stay aligned with any updates Revolut may push to their API standards. This proactive approach minimizes downtime and maintains data integrity for your finance operators.

## Inspect Rate Limits

Revolut API error 1018 typically indicates a rate limit violation, meaning your application has exceeded the allowed number of requests within a specific time window. To resolve this, you must first inspect your current usage against the limits defined in your Revolut developer dashboard. Often, this error arises from aggressive polling or unoptimized batch operations that trigger multiple API calls simultaneously. Check your recent request logs to identify which endpoints are consuming the most quota. If you are processing high volumes of transactions, consider implementing exponential backoff strategies to automatically delay subsequent requests when limits approach their thresholds. This prevents immediate rejection and allows your system to gracefully handle temporary throttling without losing data integrity or disrupting operational workflows.

Additionally, review your account tier and any custom limits set by Revolut support. Standard accounts may have stricter constraints compared to enterprise plans, so upgrading or requesting a limit increase could be a viable long-term solution. Ensure your integration correctly handles HTTP 429 responses by caching responses where possible and reducing redundant calls. For mosa.money’s B2B treasury platform, optimizing payment batch sizes and synchronizing data updates during off-peak hours can significantly reduce peak load. By aligning your request patterns with Revolut’s rate policies, you can maintain seamless multi-rail payment processing without encountering disruptive error 1018 interruptions, ensuring consistent service availability for finance operators relying on your platform for critical treasury operations.

## Contact Support

Revolut API error 1018 typically indicates a specific validation failure within your payment routing logic, often stemming from mismatched currency codes or unsupported beneficiary details in your transaction payload. To resolve this, you must first verify that the ISO 4217 currency code in your request matches the account’s primary currency exactly. Many developers overlook subtle discrepancies, such as using USD instead of the localized variant required by certain European accounts. Ensure your API headers contain the correct authorization token with sufficient permissions for the specific endpoint you are calling. If the token is valid, inspect the JSON body for any deprecated fields that may have been removed in recent Revolut platform updates. Cross-reference your integration with the latest developer documentation to confirm that all mandatory parameters are present and correctly formatted.

If the validation checks pass but the error persists, the issue may lie in the underlying bank’s processing rules rather than your code. In such cases, reaching out to Revolut’s technical support team with your request ID is crucial. Provide them with the full payload and response headers to expedite their diagnosis. As a B2B treasury operator using mosa.money, you can also leverage our dedicated support channels to trace the payment rail’s status. Our platform logs every interaction, allowing you to pinpoint exactly where the rejection occurred during the multi-rail payment process. By systematically verifying your configuration and engaging directly with the necessary support teams, you can restore seamless transaction flows without significant downtime for your finance operations.

## Error 1018 Troubleshooting

| Method | Effort | Success Rate | Notes |
| --- | --- | --- | --- |
| Verify API Key | Low | High | Check for typos |
| Check Permissions | Medium | Medium | Ensure scope access |
| Review Docs | Low | High | Confirm usage |
| Contact Support | High | N/A | Last resort |

Revolut API error 1018 typically indicates an authentication or permission issue within your integration. To resolve this, first verify that your API key is correct and has not expired. Next, ensure your account possesses the necessary scopes for the requested endpoint. If credentials are valid, review your request parameters for any missing required fields. Finally, consult the official documentation or contact Revolut support for specific guidance on your account status and recent changes.

## Quick answers

### What causes Revolut error 1018?

This error typically indicates an invalid API key or insufficient permissions for the requested endpoint.

### How to fix Revolut error 1018?

Regenerate your API key and ensure it has the correct scopes enabled for your integration.

### Is Revolut error 1018 a bug?

It is usually a configuration issue rather than a system bug requiring a platform update.

### Who handles Revolut error 1018?

Developers must resolve this by adjusting their authentication headers before contacting Revolut support.

Canonical: https://mosa.money/knowledge/how_do_i_resolve_revolut_api_error_1018.php
Markdown: https://mosa.money/knowledge/how_do_i_resolve_revolut_api_error_1018.php/index.md