Reasons for error code 1008 in webhook subscription request

Hi, Zapier Integrations team here.

We are experiencing users reporting being unable to set up a webhook subscription to Smartsheet when a POST request is made to https://api.smartsheet.com/2.0/webhooks

Response received

{  "errorCode": 1008,  "message": "Unable to parse request. The following error occurred: Field 'name' contains disallowed characters.",  "refId": "QEpsBh"}

For request

POST https://api.smartsheet.com/2.0/webhooksContent-Type: application/jsonuser-agent: ZapierAuthorization: :censored:33:18737dbfd2:{  "callbackUrl": "https://hooks.zapier.com/hooks/standard/XXXX/40beXXX/?challengeSource=SmartsheetCLIAPI",  "events": ["*.*"],  "name": "Updated Row webhook, id: XXXX87b91ffb411a98353486681XXXX",  "version": 1,  "scope": "sheet",  "scopeObjectId": "XXXX15597830XXXX",  "subscope": {    "columnIds": ["XXXX34788268XXXX"]  }}

The reporting users confirm there is no 'name' column in their sheet, suggesting possible internal field mapping or API-level validation differences.

Is it possible to obtain a documented list of reasons for the 1008 error that users can check their sheet for, when seeing this error? At the moment, it blocks them from using Smartsheet with Zapier all together and we have no visibility into which characters are causing this error upon subscription request for a particular sheet or column.

Thanks!

Find more posts tagged with

Sheets

Accepted answers

All comments

Georgie

Hi @ZapierIntegrations,

I’ve reached out to the relevant team and can confirm a change was made on our side that resulted in several characters including “:” being disallowed in the webhook name. Note that the "name" field is within the POST request rather than the sheet. However, the change was live for approximately one week before it was reverted at the beginning of October.

Are you still receiving reports that users are experiencing the error? Please let us know if you are, and I’ll ensure the relevant team investigates further. If users are still seeing the issue, an alternative solution while the team investigates is to avoid the use of the following characters in webhook names: <>:;%\/#"

Thanks,

Georgie

ZapierIntegrations

Hi @Georgie ,

Thanks for the response!

The most recent user reporting this behaviour was on 2 October, and checking our logs in the past 7 days, I don't see any failed requests to the subscribe endpoint. I'll go ahead and close this bug out on our end as well, as you've confirmed that change to limiting characters in subscribe requests has been resolved.

Thanks for the help!

Sign in to join the conversation!

Quick Links

Component react.discussion.discussions had an error.

ref must be one of: categoryID, siteSectionID, category, category/categoryID, category/name, category/description, category/url, category/allowedDiscussionTypes, locale, siteSection, siteSection/basePath, siteSection/contentLocale, siteSection/sectionGroup, siteSection/sectionID, siteSection/name, siteSection/description, siteSection/apps, siteSection/attributes, layoutViewType, discussionID, commentID, page, latest, sort, sortType, lookupSort, discussion, discussion/name, tags, breadcrumbs, discussionApiParams, serverDraftID, serverDraft.