SKY API - RENXT Constituent PATCH profilepicture resulting in 400 on API Console and Programmatically
Hello.
BB Customer Service told me that technical support for the RENXT APIs is available here, so I am looking for Blackbaud technical folks to investigate the cause of the error I am receiving.
When posting a photo, I have used the following flow (same as with
):
- Find constituent ID via GET /constituent/v1/constituents/search
- Create a document request via POST /constituent/v1/documents with datastructure including file_name (something.jpg) and upload_thumbnail (true)
- Receive datastructure with file_id, file_upload_request, thumbnail_id, and thumbnail_upload_request
- Upload file using file_upload_request.headers via file_upload_request.method to file_upload_request.url
- Upload file using thumbnail_upload_request.headers via thumbnail_upload_request.method to thumbnail_upload_request.url
- Note file_id and thumbnail_id
- Update Constituent via PATCH /constituent/v1/constituents/{constituent_id}/profilepicture using
- document_id = payload2_1.file_id
- thumbnail_id = payload2_1.thumbnail_id
- file_name = posted2_1.file_name
- Receive 400 with body {
"Message": "An error has occurred."
}
I am able to verify that the blob container has the pictures.
I was able to do this between 7/22 and 8/9 when I loaded >8000 photos into our TR1 conversion instance, and we are moving into TR2.
All of the steps above were completed on the SKY API Reference (try it) UI after receiving errors in the program I wrote and used last time -
There is no correlation ID or anything else I can use to provide, so I can give an appropriate person the actual payloads (minus authorization/subscription key data) that I have received to submit the image; however, I am a bit concerned with posting them on a semipublic forum.
Thank you for your time.
Michael Dzikowski
Comments
-
@Michael Dzikowski
If this has been working and suddenly stopped working, that is going to be a bug that support need to esculate to internal engineer to look into and fix, not direct you to Community.I have had my fair share of experience with BB Support not having the right expertise to handle SKY API related questions. You need to be stern with them and tell them you are not having trouble with using the API, the API has been working, and now it stopped working. Insist it is a bug that needs to be looked at.
To confirm, I did try to do this and is face with the same error you did.
@Erik Leaver I don't know if there's anything you can do to help guide this problem to the right path.
1 -
@Alex Wong With bbcon happening, support will be the best way to get this moving. @Michael Dzikowski please open a support ticket, reference this community post, communicate with your CSM & provide them the case number. Please let your CSM know you might need some help from the SKY API team and they should be able to help.
1 -
@Michael Dzikowski Hey Michael. I'm the dev who's currently assigned to this bug, and since the support analyst linked to this thread, I figured I'd hop in. Are you able to hit to this endpoint successfully when you exclude the thumbnail id from the request? It's not a required property, and I was able to make these PATCH requests when I left it out.
0 -
@Heather Noble
Thank you for reaching out. Oddly enough, yes, I am. Since Jonathon noted your request for me to try one, I figured I'd try more and then today I decided to run with it and run some larger batches. I just tried with several thousand requests and it does work just fine (minus me going over the call quota ?). I changed my code to not request thumbnail (upload_thumbnail = false) and then I left that property out of the PATCH - it seems to work. It doesn't appear to interfere with the operations side; I've reviewed a couple dozen records and they do show the person's photo the same as the source system. The odd thing is that I had put all (over 8000) photos in July/August timeframe during our TR1 exercise with all of those submissions made (thumbnail and regular) with no issue.I have no issue just submitting the original photos and noting this to our advancement folks for them to then go in and do a verification. I just want to make sure this is something of an expected outcome.
Thanks!
Michael
0
Categories
- All Categories
- 6 Blackbaud Community Help
- 210 bbcon®
- 1.4K Blackbaud Altru®
- 395 Blackbaud Award Management™ and Blackbaud Stewardship Management™
- 1.1K Blackbaud CRM™ and Blackbaud Internet Solutions™
- 15 donorCentrics®
- 360 Blackbaud eTapestry®
- 2.5K Blackbaud Financial Edge NXT®
- 649 Blackbaud Grantmaking™
- 567 Blackbaud Education Management Solutions for Higher Education
- 3.2K Blackbaud Education Management Solutions for K-12 Schools
- 937 Blackbaud Luminate Online® and Blackbaud TeamRaiser®
- 84 JustGiving® from Blackbaud®
- 6.5K Blackbaud Raiser's Edge NXT®
- 3.7K SKY Developer
- 247 ResearchPoint™
- 119 Blackbaud Tuition Management™
- 165 Organizational Best Practices
- 239 The Tap (Just for Fun)
- 33 Blackbaud Community Challenges
- 31 PowerUp Challenges
- 3 (Open) PowerUp Challenge: Data Health
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Product Update Briefing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports+
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Email Marketing
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Gift Management
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Event Management
- 3 (Closed) Raiser's Edge NXT PowerUp Challenge: Home Page
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Standard Reports
- 4 (Closed) Raiser's Edge NXT PowerUp Challenge: Query
- 784 Community News
- 2.9K Jobs Board
- 53 Blackbaud SKY® Reporting Announcements
- 47 Blackbaud CRM Higher Ed Product Advisory Group (HE PAG)
- 19 Blackbaud CRM Product Advisory Group (BBCRM PAG)


