DESCRIPTION OF MY PROBLEM:
So basically, when I want to share a post, it works if it just involves text. But for an image share (text with images) we need to follow the method at Share on LinkedIn - LinkedIn | Microsoft Docs 5
Procedure is
Register your image to be uploaded.
Upload your image to LinkedIn.
Create the image share.
I’ve been facing this issue for a really long time now and sincerely hope someone can help me out.
I’ve got the necessary products for the newly created app on the LinkedIn Developers dashboard.
I get the return value of asset and upload URL from step 1. But I don’t know how to execute step 2 - The upload your image involves a cURL that isn’t possible on Bubble. So I tried converting it to a REST on Bubble itself.
Now after executing this (as per screenshot above), I check the status of the Asset and am getting CLIENT_ERROR there. I’ve searched everywhere and tried changing the Content-Type as well to multipart/form-data, image/png and application/json but it doesn’t seem to work.
It’ll be great if someone can help me out with this.
Related
I am working on a website with the Roblox API and was using the Asset ID to pull thumbnails of different assets in the catalog. The code below was working perfect until a few days ago.
<img src="https://www.roblox.com/asset-thumbnail/image?assetId=<?php echo get_field('roblox-item-id', $p->ID ) ?>&width=75&height=75"
Please note 'roblox-item-id' = Asset ID in my code above
The asset id is still correct because everything works on our website besides the thumbnails.
I saw a few post where a bit ago they changed the URL to get these images to rbxthumb://type=Asset&id=
This method also did not work and people who posted links to the solution in the past now have the same error I am getting.
It seems like there is some kind of undocumented change to access these thumbnails with the asset ID. Does anyone know of a way for me to access them or an alternative method I could use besides the asset id? This happened only days ago and the Roblox Dev forums don't seem to have anyone posting about it.
I've been learning postman for a few days and now I'm training my little knowledge about this topic while building my own collection using Imgur API. Everything works according to plan except for one thing.
I want to transfer an existing image using the POST method to an existing album, but all the time what I get in the response body is a meme - "nobody expects the cr/lf". I know something is wrong but can't figure out what. I do exactly what is written in the documentation.
so this is what I have:
and this is what the documentation says:
https://apidocs.imgur.com/#b98029b6-5cc1-4a6f-b4bf-fe1db50869a2
I would be very grateful if someone help me :)
My app uses LinkedIn authentication along with a couple of other social network logins.
Even though authentication is working fine, all of a sudden LinkedIn stopped returning the formatted profile picture i.e. picture-url. I do however continue to receive the original image i.e. picture-urls -- see below:
In my authentication request, I request r_basicprofile and r_emailaddress and according to this link, I should be receiving both the formatted and the original image.
https://developer.linkedin.com/docs/fields/basic-profile
Up until 10 days ago or so, I was receiving both images. I didn't make any changes to my code but for some reason, the formatted image doesn't show up anymore. Any idea why and how to fix this?
UPDATE:
All of a sudden I started getting both images again -- without making any changes to my code.
I also noticed that the image URL has now changed and I'm seeing all types of parameters in there -- such as image size, something that looks like API version type (alpha in the example below) and possibly a time stamp indicator:
https://media.licdn.com/dms/image/{image-id}/profile-displayphoto-shrink_100_100/0?e=123456789&v=alpha&t={sometypeofid}
I don't remeber seeing any of these parameters in the image URL which is not a URL at all but what seems to be an API call that returns an image.
I don't know if LinkedIn announced such changes that I missed or just decided to make these changes without keeping developers in the loop. I hope it's not the latter and I simply missed the announcement.
Can anyone help with using the Twitter API to upload a profile banner using the account/update_profile_banner? I have been searching on Google for so long and can't find any solution, thanks in advance
Based on https://gist.github.com/hayesdavis/97756
It looks like the docs are misleading, unless you are uploading a really small image, I expect it is critical to use multi part form data instead of encoding data in the query params.
Post your example code though, it's bad stackoverflow form to just say it doesn't work without showing the code and errors you are getting.
Using the Contact API v3 I had a working implementation for uploading a photo to an existing contact.
Since a couple of weeks this fails with 404. The implementation has not been changed when the API servers started to sent back 404s and I don't see any indication what exactly changed and would result now in the 404s.
I'm using HTTP PUT + the photo URL of the contact.
One interesting observation I made was that the contact's self-URL changes which each request (the provided details are still always the same and correct).
Did anyone notice something similar ?
Edit: Link to issue: http://code.google.com/a/google.com/p/apps-api-issues/issues/detail?id=3301&q=contact&colspec=API%20ID%20Type%20Status%20Priority%20Stars%20Opened%20Summary
tried different photo formats and sizes, different content types and even photos which had been uploaded previously (when it was still working). Nothing changed the behaviour of returning 404.
w.r.t to change contact ids: the contact ID changes between API invocations. I first thought it could be related to reopened connection( no keep-alive) that contact ids change. However what speaks against this being the cause of the issue is that first retrieving a contact and then editing a contact's address is possible without any issues.
authentication does not seem to be problem as well - otherwise editing a contact's address would not work as well.
PS: I'm using the JSON output format when retrieving the contact.
PS2: s/GET/PUT in step 3 ( I tried to change PUT to GET to see if it still returns 404... which it does).
PS3: am not using any client library but implement the protocol directly (which should not be relevant for the HTTP PUT on the photo link
After hours of investigation I found out that this is particular an issue using OAuth1. Using OAuth2 the exact same photo links which had been returned when requesting a specific contact record using OAuth1 work and return the photo data on HTTP GET. I expect HTTP PUT for photo links using OAuth2 to succeed as well.
Remains open if if there's some kind of workaround for OAuth1.