-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Caption are no longer supported #10
Comments
I will work on it! |
@Kan-A-Pesh @chemokita13 can you explain how to successfully call the I am calling with this body:
and am getting the following response:
|
You need to use the To post you first need to get three tokens (front photo, back photo and post) with {
"status": 201,
"message": "Photo created",
"data": {
"firstPhotoToken": "tokentokentokentoken",
"secondPhotoToken": "tokentokentokentoken",
"postDataToken": "tokentokentokentoken"
}
} Then post your photos with the After posting the two photos you can call |
@Kan-A-Pesh Hi, before I was not posting both my front photo and back photos, but am now doing it. To recap, I am able to (1) get my three tokens from
Is there a potential issue with my request:
|
Hey! @AaditT Are you sending also the login token in headers? I think isnt delcared in api docs but is necessary. I let you an example in typescript and axios const postDataToSend: { tokenData: string; postData: PostData } = {
tokenData: postDataToken,
postData: postData,
};
const responseOptions = await axiosInstance.post(
"/post/upload/data",
postDataToSend,
{
headers: {
token: token,
},
}
); |
Hi @chemokita13
but am still getting the same internal server error |
Idk, it seems an error with maybe the "taken_at" param that is harder to implement, let me research it |
When I make the api call to
post/upload/data
endpoint I get a 400 error.And when I try making the api call directly to the BeReal API, I get the same error with the following body:
I tried again without the
caption
property (directly with the BeReal API) and it works.So the captions have probably been moved to another endpoint.
The text was updated successfully, but these errors were encountered: