We’re here to help!

If you find yourself unable to access your account, follow these steps to unlock it:

1. Start by visiting our help center and reviewing the provided instructions.

2. If you haven’t received the “unlock account” email, please ensure that you have whitelisted our email address “[email protected]”. Additionally, don’t forget to check your spam folder, as the email might have been filtered there.

If you have completed these steps and still need to unlock your account, proceed with the following:

1. Go to Contentful’s login page and click the “Unlock account” link.

2. Click on the link and you will be directed to a form. Fill out the form with the email associated with your account and click “Unlock.”

3. After submitting the form, you will be redirected to the main login page. Look for a banner indicating that an email with further instructions has been sent to you. Please note that it may take a few minutes for the email to arrive in your inbox. Don’t forget also to check your Spam folder.

4. Once you receive the email, follow the provided instructions to unlock your account and regain access.

To locate your Organization ID, please follow these steps:

1. Click on your organization name in the top left corner of the web app.

2. Go to organization settings.

3. Click on organization information.

4. Your Organization ID, a 22-digit alphanumeric identifier, will be displayed.

Please note that only organization owners and admins have access to the Organization ID. If you are unable to access this information, kindly contact your organization’s owner or admin.

To find your Space ID:

1. Navigate to the desired space.

2. Click on the Settings tab, then select Space settings, and finally, choose General settings.

3. The Space ID can be found under the General section on the Space Settings page.

If you are experiencing issues with the web app not loading or encountering server errors, we recommend the following troubleshooting steps:

1. Clear your browser’s cache and cookies: Accumulated cache and cookies can sometimes interfere with the proper functioning of the web app. Clearing them can help resolve any related issues. You can usually find this option in your browser’s settings.

2. Try using a different browser: Occasionally, browser-specific issues may arise. Testing the web app in an alternative browser can help determine if the problem is specific to the current browser you are using.

3. Disable browser extensions: Some browser extensions or plugins may conflict with the web app’s functionality. Temporarily disabling them can help identify if any of the extensions are causing the issue.

By following these steps, you can eliminate common browser-related factors that may be causing the problem. If the issue persists after performing these troubleshooting steps, please reach out to our support team for further assistance.

Contentful serves as the content layer and does not directly interact with your frontend application, such as a website or app. We store your content within the defined model, and your application retrieves and displays the content through APIs. If your entry is published, it can be accessed via a direct API call to our Content Delivery API. You or your development team can test this by making a request using the following link: Content Delivery API to check for recent changes.

Here are a few considerations to investigate on the front end:

1. Are you using a static site generator like Vercel? Make sure you have set up a rebuild of your site to trigger when new content is published. You can achieve this using our webhooks feature. Learn more about webhooks.

2. Check if your frontend application has any caching mechanisms in place that could prevent a network call to Contentful. Ensure that the cache is properly invalidated or refreshed when new content is published.

Invitations are valid for a period of 7 days. If your invitation has expired, we recommend contacting your Organization Owner or Admin, who can resend the invitation to you.

What should I do if I do not receive the user invitation?

If you have not received the invitation, it is possible that it might have been filtered into your spam folder. To ensure the smooth delivery of our emails, please consider whitelisting the email address [email protected] in your email settings. This will help prevent future invitations from being misclassified as spam.

If you are using Azure as your Single Sign-On (SSO) provider, please note that it has a unique setup that differs from other SSO providers. In order for the integration to work correctly, the attribute configuration needs to be precise.

To troubleshoot the issue of missing attributes (givenname, surname, and email), please follow these steps:

1. Configure the required attributes (givenName, surname, and email) as “claims” in Azure. It’s essential to ensure that the attribute names are configured correctly without the prefix “http://schemas.xmlsoap.org/ws/2005/05/identity/claims/”. Request a screenshot of the claims setup from your Azure AD administrator and verify that the attribute names are displayed without the prefix (e.g., “givenName” instead of the complete URL).

2. Confirm that the email claim is mapped to the user:mail attribute. Unfortunately, in Azure, you cannot change the default email claim with a prefix. Therefore, ensure that the mapping is correctly set to user:mail.

3. Pay attention to the case sensitivity of the attribute names in the claims. For example, Contentful is case sensitive, so the attribute names should be configured exactly as required (e.g., givenName, surname).

4. Change default cert from SHA-256 to SHA-1.

For detailed instructions and guidance, you can refer to the official documentation provided at Azure AD SSO Configuration with Contentful.

If you encounter any further difficulties or have additional questions, please feel free to reach out to our support team for further assistance.

When you receive a 429 error on the Content Delivery API (CDA), it usually indicates a high volume of publishing activities by your team. Each publish or unpublish event triggers cache purging, which means that subsequent requests will directly hit our server while the cache is being rebuilt. These requests contribute to the per second technical limit. However, requests that are served from the cache do not count towards this limit.

To mitigate this issue, it is advisable to implement a throttling mechanism in your requesting code. This mechanism should introduce a timeout after receiving a 429 error, before making subsequent requests. This allows for a more controlled and staggered flow of requests to avoid overloading our server.

Please note that the Content Preview API (CPA) and Content Management API (CMA) do not cache requests. Consequently, each request made to these APIs will count towards the per second limit.

If the desired locale is not available in the dropdown list, you can add a custom locale programmatically. This process cannot be performed directly from the web application interface. Instead, you need to use the “Create a locale” endpoint to add the custom locale.

To accomplish this, we recommend consulting your developers who are familiar with the Contentful API. They will be able to assist you in adding the custom locale programmatically using the appropriate endpoint.

Contentful delivers your content through our CDN networks. Occasionally, latency can occur, resulting in slower content delivery. However, it is also possible that your network might be blocking the calls due to proxy or firewall settings.

To troubleshoot the issue, we recommend taking the following steps:

1. First, try making direct calls to our endpoints instead of relying on your application. This will help determine if the delay is specific to your network or application.

2. If possible, switch to a different network or internet connection. This can help eliminate the possibility of network-related issues affecting the content delivery speed.

If the issue persists after following these steps, we suggest opening a support ticket with our team. Please provide all the relevant details, including network logs, so that we can investigate further and provide appropriate assistance.