📢 #WebComponents bookmarks update: #API #design.
If you're already familiar with basics, do check it out.
You'll find some useful tips and things to consider.
Y’all See API Contract Testing Like You Do Terms of Service - https://apievangelist.com/2023/02/24/yall-see-api-contract-testing-like-you-do-terms-of-service/
Getting Pedantic About API Contract Testing https://apievangelist.com/2023/02/23/getting-pedantic-about-api-contract-testing/
How I Use Postman for Algorotoscope — API-First, No UI Needed https://apievangelist.com/2023/02/20/how-i-use-postman-for-algorotoscope-api-first-no-ui-needed/
Learning About Railroad Regulation in the Empire Express https://apievangelist.com/2023/02/20/learning-about-railroad-regulation-in-the-empire-express/
You can do a lot more with Mastodon's API than make bots. I'll show you a few examples in my latest tutorial.
https://stefanbohacek.com/blog/automating-your-mastodon-profile-with-pipedream-com
🎙️ APIs You Won't Hate (the podcast)
Our latest episode just went live!
Don't roll your own API Management tools, with Josh Twist from Zuplo
RAML and API Blueprint: Where Are They Now https://blog.postman.com/raml-and-api-blueprint-where-are-they-now/
gRPC APIs Meetup at the Microsoft Reactor https://www.meetup.com/api-craft-san-francisco/events/291296824?utm_medium=referral&utm_campaign=share-btn_savedevents_share_modal&utm_source=twitter #Meetup via @Meetup
Introducing an API to Manage Your Private API Network with More Automation - https://blog.postman.com/introducing-api-to-manage-your-private-api-network-with-automation/
Twitter delays API changes again, this time 'by a few more days' - https://www.engadget.com/twitter-delays-api-changes-again-this-time-by-a-few-more-days-225636959.html?
Small banks, fintechs ask CFPB for more time to phase out screen scraping - https://www.bankingdive.com/news/small-banks-fintechs-cfpb-phase-out-screen-scraping-apis-section-1033-open-banking/641799/
The Source of Truth for an API - https://apievangelist.com/2023/02/12/the-source-of-truth-for-an-api/
KeyHacks shows ways in which particular API keys found on a Bug Bounty Program can be used, to check if they are valid.
Some of the APIs covered in the repo:
AWS Access Key ID and Secret
Azure Application Insights APP ID and API Key
Bing Maps API Key
Bit.ly Access token
ButterCMS API Key
Calendly API Key
CircleCI Access Token
DataDog API key
Deviant Art Access Token
Deviant Art Secret
Dropbox API
Facebook Access Token
Facebook AppSecret
Firebase
Firebase Cloud Messaging (FCM)
Github client id and client secret
GitHub private SSH key
Github Token
Gitlab personal access token
GitLab runner registration token
Google Cloud Service Account credentials
Google Maps API key
Google Recaptcha key
Help Scout OAUTH
Heroku API key
Instagram Access Token
Instagram Basic Display API
Instagram Graph API
Ipstack API Key
LinkedIn OAUTH
MailGun Private Key
Microsoft Azure Tenant
Microsoft Shared Access Signatures (SAS)
NPM token
Paypal client id and secret key
PivotalTracker API Token
Razorpay API key and secret key
Shodan.io
Slack API token
Slack Webhook
Spotify Access Token
Square
Stripe Live Token
Twilio Account_sid and Auth token
Twitter API Secret
Twitter Bearer token
Visual Studio App Center API Token
YouTube API Key
Zapier Webhook Token
Zendesk Access token
Zendesk API key
https://github.com/streaak/keyhacks
#api #cybersec #cybersecurity #bugbounty #infosec #infosecurity
@WuMargaret @Perl @yarmo The #OpenFoodFacts #API, #SDKs, and their database of over 2.8 million products are also available to anyone under very permissive terms: https://openfoodfacts.org/data
And they dogfood (haha) the API with their mobile apps, so you know it’s maintained.
It's official, #Twitter is going to kill academic access and premium access to the Twitter #API.
The only 3 access levels in the future:
- Limited free
Login and write access (1500 Tweets per user token)
- Basic $100
"Low level of API usage"
- Enterprise $$$$+
Talk to your sales agent.
That's the email I got last night (the first one on the issue; for developers who don't follow the news that's the first time they read that their access will be turned off the next business day).
Still no information what "low level of API usage" means. #fedifinder hits the rate limits of current elevated access for some accounts. If those get lowered, it will affect more, even if I pay for basic access (and I have an internal resistance against that). We will have to wait for Monday, to see what it will actually look like.
There are many other unanswered questions as well. With my elevated access I can use the v1.1 and v2 API endpoints. Will that be the case in the future as well? Will the fee be per app or per developer account? What about dev and staging environments? How will the rate limits look like? Volume limits? Per app or per authenticated user limits?
The #XML spec is 25 years old today.
Provide Blog Metadata via JSON-LD - kiko.io https://kiko.io/post/Provide-Blog-Metadata-via-JSON-LD/
Making sense of the technology, business and politics of APIs since 2010, then attempting to share stories about what matters to business and more technical users.