I’ve checked the Airtable API docs multiple times but can’t seem to get the syntax right for field filtering in Shortcuts. Has anyone successfully used field parameters with Airtable API in the Shortcuts app? What am I doing wrong with the URL format?
You’re using the right syntax for some API clients, but not for Shortcuts URL parameters. Shortcuts expects plain values without array notation. I hit this same wall migrating from Postman to Shortcuts last month. Shortcuts passes URL parameters as-is - it doesn’t interpret brackets as array syntax. Your current format treats [‘Title’] as one parameter value instead of an array with Title in it. Use fields=Title for single fields or fields=Title,Description for multiple fields. If your field names have spaces or special characters, add a URL encode action before the API call (though I rarely need this with standard field names). Debugging tip that saved me: use the Text action to build your complete URL first, then preview it before sending. You’ll see exactly what Shortcuts is actually sending to Airtable.
yep, those square brackets are the prob. just use fields=Title no brackets or quotes needed. had the same issue, ended up Shortcuts treated the brackets like literal text, not array stuff. also, keep an eye on extra spaces in the field name, Airtable’s API is kinda picky.
Your fields parameter formatting is incorrect. Instead of using square brackets or quotes, you should list the field names directly. For instance, use fields=Title for a single field, or fields=Title,Description,Status when specifying multiple fields. I’ve encountered this issue myself when I began using the Airtable API with Shortcuts. Be mindful that URL encoding can complicate things; if you continue to have issues, consider adding a URL encode action before making your API call. Additionally, ensure that your field names exactly match those in your Airtable base, as spaces and special characters are significant.
Shortcuts sometimes auto-adds weird encoding to URLs - that’s what tripped me up. If you’re still getting errors, build the URL in a separate text action first, then pass it to your API call. Way easier to debug what’s actually being sent.
Double check your field names are exactly right. Case sensitive and spaces matter.