4259 links
  • Arnaud's links
  • Home
  • RSS Feed
  • Tag cloud
  • Login
search: tag:api — newest first
  • Known Limits and Service Quotas - Amazon EKS

    AssignPrivateIpAddresses
    UnassignPrivateIpAddresses
    AttachNetworkInterface
    CreateNetworkInterface

    • https://docs.aws.amazon.com/ec2/latest/devguide/ec2-api-throttling.html (how to ask for limit increase)

    • https://docs.aws.amazon.com/ec2/latest/devguide/monitor.html (how to enable metrics)

    December 21, 2025 - permalink - https://docs.aws.amazon.com/eks/latest/best-practices/known_limits_and_service_quotas.html#_aws_request_throttling
    api aws cni limit rate throttle
  • Actions, resources, and condition keys for AWS services - Service Authorization Reference

    google iam resources list

    September 5, 2022 - permalink - https://docs.aws.amazon.com/service-authorization/latest/reference/reference_policies_actions-resources-contextkeys.html
    api iam
  • GitHub - Eloise1988/COINGECKO: CoinGecko Real Time Spreadsheet Feed: Prices, Volumes, Market Cap
    February 10, 2022 - permalink - https://github.com/Eloise1988/COINGECKO
    api crypto finance sheet
  • Crypto Prices | Prices for Crypto Currency Coins
    February 10, 2022 - permalink - https://cryptoprices.cc/
    api crypto finance
  • bunq API Documentation

    Une banque avec une api ouverte

    January 8, 2020 - permalink - https://doc.bunq.com/
    api banque finance
  • JSON Web Token Introduction - jwt.io
    August 5, 2018 - permalink - https://jwt.io/introduction/
    api json jwt
  • JSON API — Latest Specification (v1.0)
    August 5, 2018 - permalink - http://jsonapi.org/format/
    api format json jsonapi
  • javascript - Is a list/array valid JSON? - Stack Overflow

    31
    down vote
    accepted

    Both forms are valid. However, for an API, I would recommend the second form. The reason is that it gives you a path for expansion of your API.

    For example, if you have an API getUsersInGroup which returns an array of user objects, and later you decide you want to include, say, some aggregate statistics about the users being returned, there's no easy way to do that without breaking existing clients (or including lots of redundant data in each user object). If you use an object, you simply add another field to the object which is silently ignored by clients on a previous version of the API.

    In short, try to avoid top-level primitives wherever possible in your API, and you'll find it easier to expand in the future.

    March 26, 2018 - permalink - https://stackoverflow.com/questions/19623339/is-a-list-array-valid-json
    api json
  • Newer docker client with older Docker host - Server Fault

    :~$ docker -H tcp://10.73.204.73:2375 ps
    Error response from daemon: client is newer than server (client API version: 1.24, server API version: 1.19)

    :~$ DOCKER_API_VERSION=1.19 docker -H tcp://x.x.x.x:xxxx ps
    CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

    July 6, 2017 - permalink - https://serverfault.com/questions/664999/newer-docker-client-with-older-docker-host
    api client dcoker version
  • neurogeek/haproxyctl: HAProxy control tool

    via Doo

    February 19, 2016 - permalink - https://github.com/neurogeek/haproxyctl
    api haproxy
  • httpbin(1): HTTP Client Testing Service

    Peut etre utile

    • https://github.com/vcr/vcr
    • https://github.com/kevin1024/vcrpy
    June 12, 2015 - permalink - http://httpbin.org/
    api http service test
  • Kong - Open-Source API Management Layer
    April 29, 2015 - permalink - http://getkong.org/
    api nginx
  • Consuming JSON REST resource through HTTP - Ruby Intro
    April 18, 2014 - permalink - http://nizhu.github.io/ruby-intro-site/blog/2013/07/31/consuming-json-rest-resource-through-http/
    api puppetdb rest ruby
  • Utiliser l'api de pocket avec curl

    Compliquées ces api.. je me mets ça de côté pour plus tard car j'ai mis du temps à capter :

    http://getpocket.com/developer/docs/authentication

    D'abord il faut une consumer_key : voir la doc pour ça, c'est facile (= une api key)

    Grâce à cette clé on peut avoir un TOKEN comme ça :

    curl -X POST https://getpocket.com/v3/oauth/request --verbose --header 'Content-Type: application/json; charset=UTF8' --header 'X-Accept: application/json' --data '{"consumer_key":"CONSUMER_KEY","redirect_uri":"http://wallabag.org"}'

    On utilise ce token pour dire à pocket qu'on autorise l'application

    https://getpocket.com/auth/authorize?request_token=TOKEN&redirect_uri=http://wallabag.org

    +

    curl -X POST https://getpocket.com/v3/oauth/authorize --verbose --header 'Content-Type: application/json; charset=UTF8' --header 'X-Accept: application/json' --data '{"consumer_key":"CONSUMER_KEY","code":"TOKEN"}'

    donne un ACCESS_TOKEN

    on a enfin l'ACCESS_TOKEN, on peut requeter l'api :

    curl -X POST https://getpocket.com/v3/get --verbose --header 'Content-Type: application/json; charset=UTF8' --header 'X-Accept: application/json' --data '{"consumer_key":"CONSUMER_KEY","access_token":"ACCESS_TOKEN"}'

    April 17, 2014 - permalink - https://links.infomee.fr/shaare/C30Glg
    api pocket
  • POST vs. PUT : la confusion | Blog Xebia France

    Article intéressant sur l'implementation d'api REST et que faire/ne pas faire concernant le mapping CRUD <=> http methods

    March 18, 2014 - permalink - http://blog.xebia.fr/2014/03/17/post-vs-put-la-confusion/
    api crud rest