Home
Events
Groups
Members

00 Clay Announcements
01 Community General
01 Props and Wins
01 Watercooler
01 Welcome and Intros
02 Bugs
02 Starting with Clay
02 Support
03 Feedback & Requests
03 Tutorials & Inspiration
04 FT Job Opps
Gtm Career Advice
Member Spotlight

Community Guidelines

Powered by Tightknit

Setting Up HTTP/API for DotDigital in Clay

·

·

Hello, need help setting up an HTTP/API within Clay for a sequencer called DotDigital. They don't use keys but rather API user and password

Setting Up HTTP/API for DotDigital in Clay | Clay

7 comments

· Sorted by Oldest

Channeled
APP
·
·
To set up an HTTP/API for DotDigital in Clay using an API user and password, follow these steps: 1. In Clay, create a new HTTP API integration. 2. Choose the appropriate HTTP method (GET, POST, PUT, or DELETE) based on your needs. 3. Enter the DotDigital API endpoint URL. 4. In the Headers section, add an "Authorization" header. Use Basic Authentication by encoding your API user and password in Base64 format. 5. Configure any necessary query parameters or request body. If you encounter any JSON-related issues, please copy and paste the JSON into the chat for further troubleshooting.
Sources: HTTP API with JWT authentication | Documentation | Clay University HTTP API with Clay HTTP API integration overview | Documentation | Clay University
Bo (Clay)
·
·
Hey Eugene, In this case, you’d usually include the API user and password in the request headers or as part of the query, depending on how DotDigital expects authentication. Feel free to send over the DotDigital API docs or try setting it up in your table—happy to take a look and help troubleshoot if anything’s off.
Eugene Asem
·
·
Hi Bo
Eugene Asem
·
·
Here you go: https://developer.dotdigital.com/docs/getting-started-with-the-api
Eugene Asem
·
·
Table: https://app.clay.com/workspaces/394562/workbooks/wb_7EJuxTCBfx26/tables/t_iwkphcVANvZM/views/gv_ZUB5ZqwhyYES
Mark (Clay)
·
·
Hi Eugene. When we click on an individual cell, a side panel should open up for the Cell Details. The error I see is: LBKSClay received a undefined error from the API with Content: Invalid character in header content ["Authorization"]LBKSI believe the issue is that the Authorization value had a line break. So we needed to change this: LBKSBasic YXB...LBKSTo this: LBKSBasic YXB...LBKS
Channeled
APP
·
·