Hey, I’m trying to create a custom object via API in a dev portal we’ve created so we can experiment a little, we already created this object in our active production environmnet. We get the following (this is the truncated version) error:
The scope needed for this API call isn’t available for public use. If you have questions, contact support or post in our developer forum."
“correlationId”: “6d3547a3-a2ab-407c-91b3-309b9695b855”,
“category”: “MISSING_SCOPES”
What gives?
Hi @YBarOr,
Off the top of my head I have not seen this error before. Could you share the request that you are making that gives this error?
Yup, trying to set up a custom object in our test environment:
{
“name”: “customer_record”,
“labels”: {
“singular”: “Customer Record”,
“plural”: “Customer Records”
},
“primaryDisplayProperty”: “client_name”,
“requiredProperties”: [
“client_name”
],
“properties”: [
{
“name”: “client_name”,
“label”: “Client name”,
“type”: “string”,
“fieldType”: “text”
}
],
“associatedObjects”: [
“CONTACT”,
“COMPANY”,
“DEAL”
]
}
Could you share the URL as well?
https://api.hubapi.com/crm/v3/schemas?hapikey=********************* (not putting an API key here, sorry)
@YBarOr ,
I loked into this endpoint, and it looks like there is an issue on HubSpots side currently, I coppied the exact requests from the documentation, but I recieved the same error. I can only assume that the issue is with HubSpot here. I’ll go ahead and ping some people from HubSpot, to get some internal eyes on this. @dennisedson @sharonlicari
Thanks a lot, I’m dying to hear what they think of this.
Cheers!
Apologies for delayed response. Just getting back from vacation.
Like @Willson , I am unable to reproduce in a test portal. I used the code above for my test (see screengrab).
@YBarOr , could you send me your portal id that you are working with?
@JBeatty , if you are getting the same error, could you also send your portal id?
After doing some further testing in a few different portals it seems, that it is failing with that error when the portal does not have an enterprise subscrption. I didn’t realize last week, becuase the test portal that I tested it in had just expired. Doing it in a new test portal with enterprsise scope allievated the issue. @YBarOr, can you confrim that you do have an enterprise subscription on the portal? And, @dennisedson, I do not asee a screengrab in your post.
The issue was resolved by re-enabling the “trial” for the sandbox portal.
So to re-iterate - make sure the test portal is opened from an enterprise dev account, and that the 90 day trial is re-enabled. Custom objects can now be freely created.
