Error getspace with non master enviroment accessToken

Expected Behavior

My API key has access to QA environment only. But before initial request I would like to call getSpace. And received 404

Actual Behavior, Possible Solution

Set space and environment

Environment

QA

• Language Version: 11*
• Operating System: Ubuntu
• Package Version: 2.1.47
• Which API are you using?: Delivery / Preview

[nimajneb]

@Khaledgarbaya Thank you for looking into this. I understand and I can also confirm that everything works when granting the API key access to the master environment.

Here’s some background: In our project, we’re consuming the Contentful API with the gatsby-source-contentful plugin. When fetching the content, the plugin uses getSpace(), probably to get some metadata from it. However, if the configured API key does not have access to the master space, an exception is thrown, which essentially breaks the build.

As it might not always be desirable to grant certain API keys access to the master environment, even during development, I think I should maybe report this in the gatsby project and see if there’s some solution, even if it’s only a note in the docs.

[nimajneb]

@Khaledgarbaya

Get space will try to get data about your master environment and since you didn’t have access to it the API returns the error

Hi! I was just debugging the same problem before finding this issue.

If I understand the documentation at https://www.contentful.com/developers/docs/concepts/multiple-environments/ correctly, and a sandbox environment acts as kind of an override for specific space information, should getSpace then really get the data of the master environment’s space?

Here’s my code that failed:

const client = contentful.createClient({
  space: 'my-space-id',
  accessToken: 'my-access-token', // my-access-token does have access to test-environment, but not to master
  environment: 'test-environment',
});
try {
  const space = await client.getSpace();
} catch (e) {
  // ...
}

I’d expect space to contain the space information for the environment specified in createClient, but instead the client.getSpace() call actually throws an exception with a 404 error, just like mentioned by the OP.

This feels like a bug to me. Or do I misunderstand something here?