获取缺少参数＆＃x27;调用QUIP API时出错 - 添加成员方法
我正在尝试使用QUIP Admin和Automation API将成员从Salesforce Trigger中添加到文档中。 我已经成功使用了GET方法来验证令牌并从自动化API中获取用户，但是当我调用Admin API添加成员时，我会遇到错误。尽管传递了有效的线程ID，但我遇到的错误是“丢失参数thread_id”。如果我将尸体从请求复制到邮递员中，则可以正常工作。 Salesforce组织是开发人员沙箱。
这些是salesforce的调试线：
332] | debug | system.httprequest [endpoint = https：//platform.quip.com/1/admin/admin/threads/add-members？
user_debug [ [336] | debug | body req = {“ thread_id”：“ enivacadicco”，“ member_ids”：“ kpdafrztnrw”}
user_debug [337] | debug | debug | debug | body响应= | body worse = {“ application_error”，“ application_error”，“ errive_code”，“”：400：400：400：400 ，“ error_description”：“缺少参数'thread_id'”}
user_debug [339] | debug | debug | debug | post user_debug
scope | scope = scope = user_read admin_manage user_debug [341]
[340] | debug | /+mbewzx5lxaei/q/ykxsmhc9pjc =
任何帮助将不胜感激
I'm trying to use the Quip admin and automation APIs to add members to a document from a Salesforce trigger.
I've successfully used the GET methods for verify token and get user from the automation API, but I'm getting an error when I call add members from the Admin API. The error I'm getting is 'Missing argument thread_id', despite passing in a valid thread id. If I copy the body from the request into Postman it works fine. The Salesforce org is a developer sandbox.
These are the debug lines from Salesforce:
USER_DEBUG [332]|DEBUG|System.HttpRequest[Endpoint=https://platform.quip.com/1/admin/threads/add-members?company_id=JKNAcB0VIMy, Method=POST]
USER_DEBUG [336]|DEBUG|Body req = {"thread_id":"eNiVAcaDICco","member_ids":"KPDAFRZtNRW"}
USER_DEBUG [337]|DEBUG|Body response = {"error":"application_error","error_code":400,"error_description":"Missing argument 'thread_id'"}
USER_DEBUG [339]|DEBUG|Method = POST
USER_DEBUG [340]|DEBUG|Scope = USER_READ ADMIN_MANAGE
USER_DEBUG [341]|DEBUG|Authorisation = Bearer UkRQQU1AcXymZ1M=|1692717157|N4CCVoKA8MY4sNF/+mBeWzX5lXAeI/q/YKxSMhC9PJc=
Any help would be much appreciated
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我发现了这个问题，它是标题中的内容类型，需要将其设置为应用程序/JSON
I found the issue, it was the content-type in the header, it needed to be set to set to application/json