Error: "403 Forbidden" with Code References

Affected: Code References

Symptoms

When using code references, calls to the LaunchDarkly API fail with a 403 Forbidden error.

Cause

This error occurs when the API access token lacks the required permissions.

Common causes include:

• The token does not have write permission for the code-reference-repository resource.

• The token can modify a resource, but cannot view the project it belongs to, such as when the role is based on no_access and is missing the viewProject action.

Solution

1. Confirm the API access token has write permission for the code-reference-repository resource. You can grant this through a base role, a LaunchDarkly-provided project role, or a custom role. To learn more, read: Code references.

2. If the token permissions look correct but you still get a 403, confirm the role can view the project that contains the code references repository:

   1. If the role was created from no_access, make sure it includes the viewProject action. To learn more, read: Error: "Your administrator hasn’t given you permission to do anything yet."