如何通过Stitch Connect API代生成Import API集成的访问令牌？

Hey there, I've dealt with similar Stitch API quirks before, so let's walk through the possible fixes for your issue where the Import API token isn't showing up in the source properties after creation:

• Force token generation on source creation
  It sounds like the auto-token generation behavior changed recently. Even if it's not in the public docs, try adding a generate_token: true flag in the properties object of your POST request to create the Import API source. Some APIs hide these "opt-in" parameters in updates, and this might trigger the token to be generated and returned in the response.

• Use a dedicated token creation endpoint
  Stitch likely has a separate endpoint for generating Import API tokens for existing sources. Try sending a POST request to /v2/sources/{SOURCE_ID}/import-api-tokens (replace {SOURCE_ID} with the ID of the Import API source you created). Include a simple request body like {"name": "Auto-generated token"}—this should return the new token in the response. Remember, you can only have 2 tokens per source, so handle this carefully.

• Double-check your Connect API permissions
  As a Stitch Connect partner, make sure your API token has the necessary scopes to manage Import API tokens. Look for scopes like sources:import-api:tokens:write when generating your Connect token—if this scope is missing, you won't be able to auto-generate tokens programmatically.

• Verify API version and request format
  Ensure you're using the latest version of the Connect API (v2 is current as of now). Older API versions might have deprecated the auto-token feature. Also, confirm your source_type is set to import-api in the creation request—missing this could lead to incomplete source setup that skips token generation.

• Reach out to Stitch support directly
  If none of the above works, you've already exhausted the public docs, so this is likely an internal API change or bug. Since you're a partner, Stitch's support team should prioritize your request—explain that this functionality worked previously and now the token is missing from the source properties. They can either share undocumented endpoints or fix the issue on their end.

A quick reminder: Connect API tokens and Import API tokens are completely separate—don't mix up their uses, and keep in mind the 2-token limit per Import API source.

内容的提问来源于stack exchange，提问作者SpiritBob