Kaj je APY (Annualized Percentage Yield) v Crypto?

V tej objavi boste izvedeli, kaj je APY (Annualized Percentage Yield) v Crypto? kako deluje v kriptovaluti in naložbene priložnosti, kjer je APY pomemben.

Kaj je APY?

APY je letna stopnja donosa naložbe, ki vključuje sestavljene obresti, ki rastejo ali rastejo s stanjem. Sestavljene obresti vključujejo obresti, pridobljene od začetnega depozita, plus obresti, pridobljene od teh obresti.

Čeprav je običajno povezan s tradicionalnim varčevanjem, je APY ključna metrika za programe varčevanja s kriptovalutami in deluje podobno. Vlagatelji v kriptovalute lahko zaslužijo APY na kriptovalutah tako, da jih vložijo, jih položijo na varčevalne račune ali zagotovijo likvidnost likvidnostnim združenjem prek kmetovanja donosov. 

Hitro lahko začnete služiti APY na svoji kriptovaluti prek menjalnic kriptovalut, denarnic in DeFi Decentralized Finance (DeFi) prevzame decentraliziran koncept blockchaina in ga uporablja v svetu financ. Zgradite... protokole.

Običajno bodo vlagatelji zaslužili obresti za isto kriptovaluto kot tisto, v kateri so položili. Vendar pa obstajajo primeri, ko jih je mogoče plačati v isti ali drugi valuti.

Preprosta obrestna mera v primerjavi z letnim odstotkom donosa

Medtem ko se APY nanaša na predvideno stopnjo letnega donosa, pridobljenega na depozit ali delež po obračunavanju sestavljenih obresti, enostavna obrestna mera upošteva le obresti, zaslužene za prvotni delež. Glavna razlika je torej v tem, da APY upošteva učinke sestavljenih obresti, če se uporabljajo. 

Združevanje je močno naložbeno orodje, saj vam omogoča, da sčasoma zaslužite dodaten dohodek. V določenem obdobju se obračunavajo sestavljene obresti, dodana vrednost pa se doda v stanje. Z vsakim dodatnim obdobjem se povečajo tudi plačane obresti na celotno stanje.

Za lažje razumevanje razmislite o založbi 1000 $ po 12-odstotni letni obrestni meri januarja 2021. Po enem letu januarja 2022 boste z uporabo preprostega izračuna obrestne mere prejeli skupno 1000 × (1 + 12 %) = 1120 $.

Isti 1000 $, zastavljeni pri 12 % letno, vendar z dvoletnim združevanjem obresti v prvih šestih mesecih, vam bo prineslo 1000 × (1 + 6 %) = 1060 $ ali skupno po šestih mesecih.

Po enem letu boste zaslužili 1060 × (1+ 6%) = 1123,60 $ 

Ti dodatni 3,60 $ prihajajo iz moči sestavljenih obresti. Zato je vaš letni odstotni donos donos, ki ga boste prejeli v letu: 1123,6 $ ÷ 1000 $ − 1 ali 12,36 %.

Kako 7-dnevni APY deluje v Crypto? 

7-dnevni APY je letni donos z uporabo 7-dnevne donose. Izračuna se tako, da se vzame neto razlika v ceni izpred 7 dni in danes ter ustvari letni odstotek. 

Formula za izračun 7-dnevnega APY je naslednja:

APY = (X − Y − Z) ÷ Y × 365/7

Kje:

X = cena na koncu 7-dnevnega obdobja

Y = cena na začetku 7-dnevnega obdobja 

Z = morebitne pristojbine za teden

Ta izračunani znesek pomaga vlagateljem razumeti tedenski donos ali donos.

Ali APY predstavlja končni zaslužek?

APY predstavlja vašo stopnjo donosa ali znesek dobička ali zaslužka, ki ga lahko ustvarite. Glede na to, kako dolgo se boste odločili vložiti svoje kovance, se bo vaš končni zaslužek razlikoval. Obdobje zadrževanja bo določilo, koliko dejansko zaslužite. 

Kako izračunati APY v Crypto

APY meri stopnjo donosa, ki se letno zasluži kot dobiček od katere koli vsote denarja ali naložbe po upoštevanju sestave. 

Formula za izračun APY je naslednja:

APY = (1 + r/n) ⁿ   − 1

Kje:

r = periodična stopnja donosa (ali letna APR)

n = število obračunskih obdobij vsako leto

Izračun APY v kriptovalutih je enak kot pri tradicionalnih financah, podoben cilj pa je doseči odstotek donosa.

Vendar pa obstajajo tudi drugi načini izračuna APY, odvisno od izmenjav. APY se izračuna v preprosti obrestni obliki, kjer dnevni donos predstavlja obrestno mero, ki bo nakazana v vašo denarnico, odvisno od števila žetonov, ki ste jih zastavili. 

Formula je naslednja:

Dnevni donos = število skupnih zastavljenih žetonov × (APY za vloženi žeton ÷ 365)

Če ste na primer vložili 10.000 USDT za zajamčeni APY pri 9%, lahko naslednji dan zberete zaokroženo na najbližje celo število 2,5 USDT. Izračun je predstavljen kot 10.000 × (0,09 ÷ 365) = 2,4657 USDT.

Če pa ste se po zbiranju dnevnih donosov odločili odstraniti svoje žetone, donos ne bo pripisan na vaš račun. V bistvu bodo kakršne koli spremembe začetnega zastavljenega sredstva vplivale na dnevni donos. 

Kakšna je letna odstotna stopnja (APR)? 

APR ali letna odstotna obrestna mera je obresti, ki jih zaslužite od svojih vloženih sredstev v enem letu, izražene v odstotkih. Ta številka lahko vključuje pristojbine, ki jih plačajo posojilojemalci. Je uporabno orodje za primerjavo različnih naložbenih produktov, saj zagotavlja dosledno osnovo za predstavitev letnih podatkov o obrestnih merah. 

APY in APR zvenita zelo podobno. Vendar za razliko od APY APR ne vpliva na sestavo.

Če na primer zastavite 10.000 kovancev pri 10-odstotni APR, boste po enem letu zaslužili 1.000 kovancev kot obresti. Toda z APY se situacija bistveno spremeni. 

Za izračun APR lahko uporabite naslednjo formulo: 

APR = [(Provizije + obresti) ÷ glavnica] ÷ n × 365 × 100 

Kje:

P = glavna naložba 

N = število dni v mandatu

V tradicionalnih financah se APR pogosto uporablja za razpravo o pogojih za posojilojemalce, na primer o obrestni meri kreditne kartice, ki jo morajo posojilojemalci plačati. Ta obrestna mera se lahko nanaša tudi na odstotek, plačan vlagateljem. Na splošno je APY za posojilo višji od ustreznega APR zaradi učinkov združevanja.

Najboljše borze za trgovanje z žetoni in kovanci. Sledite navodilom in zaslužite neomejeno

☞ Binance ☞ Poloniex ☞ Bitfinex ☞ Huobi ☞ MXC ☞ ProBIT ☞ Gate.io ☞ Coinbase

 

Dejavniki, ki vplivajo na Crypto APY

Inflacija

Inflacija se nanaša na izgubo vrednosti valute skozi čas. Znotraj kriptovalute se inflacija nanaša na proces dodajanja novih žetonov v omrežje blockchain, običajno po vnaprej določeni stopnji. Privlačnost kriptovalut, kot je Bitcoin, je, da so zasnovane tako, da imajo predvidljivo in nizko stopnjo inflacije. 

Stopnja inflacije za posamezno omrežje vpliva na donose. Če ima vaš kovanec inflacijo, višjo od vašega APY, potem vaš zaslužek erodira prav tako hitro, kot ga dodate.

Ponudba in povpraševanje

Kot v vsakem tržnem gospodarstvu zakon ponudbe in povpraševanja vpliva na cene. Lastnik kriptovalute lahko učinkovito posodi svoje kriptovalute za ustvarjanje prihodkov od obresti. Ker se obresti zaslužijo na podlagi povpraševanja po izposoji te kriptovalute, lahko dinamika trga določi obrestne mere. 

Obrestna mera za izposojo denarja je ponavadi nižja, če je ponudbe veliko, in višja, ko je malo. Podobno je kripto APY spremenljiv in se spreminja glede na raven povpraševanja in likvidnost vsakega kovanca.

Sestavljena obdobja

Na izračun APY vpliva tudi količina uporabljene mešanice, ki se lahko razlikuje. Ne pozabite, da se APY poveča, če se poveča število obdobij sestavljanja. 

Poglejmo primer. Če položite 100.000 $, ki jih mesečno poplačate s 5% letno, bo vaš APY 5,116%. Uporabljeni izračun je 100.000 × (1 + 0,05 ÷ 12)^(12). Vaše stanje bo do konca leta znašalo 105.116 $. 

Po drugi strani, če se sestave izvajajo na dnevni osnovi, bo vaše končno stanje do konca leta 105.127 $ s 5,126 % APY. Uporabljeni izračun je 100.000 × (1 + 0,05 ÷ 365)^(365).

Več priložnosti za rast vašega zanimanja, več lahko zaslužite. 

Kripto naložbe, ki vključujejo APY

Če ste tip HODLing, vam ni treba samo shraniti svoje kriptovalute v denarnico in čakati, da se ceni.

Obstajajo načini za vlaganje svoje kriptovalute in črpanje iz čarovnije sestavljenih obresti ali APY, da povečate in pomnožite svoja sredstva.

Posojila in izposoja kripto valut

Če je vaše ciljno časovno obdobje v kriptovalutih dolgoročno, lahko s kripto posojanjem pridobite veliko več kilometrine od svojih sredstev.

Kripto posojanje deluje skoraj enako kot tradicionalno posojanje, vendar brez vse birokracije in papirologije. Poleg tega posojate kriptovaluto in ne papirnati denar. Ko svoje kriptovalute na decentralizirani platformi daste posojilojemalcem, zaslužite obresti ali kripto dividende. Glede na platformo se lahko obrestne mere gibljejo od 3% do 17%. 

Medtem ko kriptoposojila vlagateljem zagotavljajo pasivni dohodek, imajo posojilojemalci koristi tudi od uživanja dodatne likvidnosti. 

Kripto izposojanje

Recimo, da imate 10 BTC in nujno potrebujete nekaj gotovine — vendar ne želite prodati nobene svoje kriptovalute, ker verjamete, da bo vrednost v prihodnosti parabolična. Bojite se, da bi lahko, če odložite svoj Bitcoin, na koncu imeli manj kriptovalut, ko jih boste pozneje odkupili. 

Torej, kaj lahko storite?

Platforme za kripto posojanje vam bodo omogočile, da svojih 10 BTC uporabite kot zavarovanje in prejmete posojilo. Upoštevajte pa, da boste morda morali »prezavarovati«, kar je domiseln način, da rečete, da boste morali zakleniti veliko več kriptovalut kot znesek, ki ga želite vzeti kot posojilo. 

Ko v celoti odplačate svoje posojilo, bo vaš zavarovani BTC vrnjen – in če vam je trg naklonjen, se je ta BTC morda cenil.

Kripto posojanje

Platforme za posojanje povezujejo kriptoposojilodajalce z posojilojemalci. Evo, kako deluje kriptoposojilo:

Posojilojemalec zahteva posojilo pri posojilni platformi. Ko platforma odobri zahtevo, mora posojilojemalec založiti nekaj svojih kripto valut kot zavarovanje za posojilo. Posojilodajalec financira posojilo in občasno prejema plačila obresti po dogovorjenem APY. To se nadaljuje do konca posojilne dobe.

Posojilojemalec vrne celoten znesek posojila, šele nato se vrne zavarovana kripta.

Vlaganje v kriptovalute je preprosto. Najprej poiščite dobro posojilno platformo. Obstajata dve vrsti: decentralizirane in centralizirane platforme. Pametne pogodbe upravljajo platforme za decentralizirano posojilo brez kakršnega koli posredovanja. Nasprotno pa centralizirane platforme vključujejo tretjo osebo, ki upravlja postopek posojanja. 

Preden se prijavite na platformo za posojila, opravite skrbnost in se prepričajte, da je ugledna. Nato potrdite in primerjajte ponujeni APY, da kar najbolje izkoristite svoja digitalna sredstva.

Kmetovanje pridelka

Kmetovanje pridelka se nanaša na proaktivno posojanje vaših kripto sredstev, da bi ustvarili več kripto. Kmetje, ki pridelujejo, premikajo svoja sredstva po različnih trgih v iskanju najvišjega donosa in pristop obravnavajo kot strategijo trgovanja. Najuspešnejši kmetje nenehno spremljajo APY in izkoriščajo najbolj donosne priložnosti. Kmetje, ki pridelujejo, običajno zaslužijo veliko višje obrestne mere, kot bi jih prihranili v fiat valutah v banki.

Kripto zastavljanje

Kripto zastavljanje je način zaslužka nagrad z vašo kriptovaluto s potrjevanjem transakcij kriptovalute v omrežju blockchain. V bistvu lahko ustvarite svoj dohodek v omrežjih PoS, ki združujejo zainteresirane strani, da preverijo omrežje. Ne samo, da varujete omrežje, ampak pri tem zaslužite kripto.

Več kovancev kot date v omrežje, večja je verjetnost, da boste izbrani kot validator za dodajanje blokov v verigo blokov. Za razliko od kripto rudarjenja, za pridobivanje nagrad ne potrebujete posebne strojne opreme. Ko zastavite, zaklenete svojo kripto in jo za določeno obdobje vzamete iz obtoka. To učinkovito omejuje ponudbo kovanca, kar lahko pozitivno vpliva tudi na njegovo vrednost.

Kaj lahko storite z zasluženimi obrestmi? 

Zaslužene obresti gredo v vaš portfelj kot dobiček, zaslužen z relativno malo dela. To je definicija pasivnega dohodka. Lahko še naprej poskušate zaslužiti več obresti od tega dohodka ali pa vzamete zaslužene obresti in jih uporabite za trgovanje. Trg kriptovalut je zrel za priložnosti za trgovanje s kriptovalutami in izvedenimi finančnimi instrumenti. 

Prometno trgovanje s kriptovalutami pomeni nakup in prodajo kriptovalut po trenutnih tržnih tečajih na borzi. Trgujete lahko tudi z izvedenimi finančnimi instrumenti, ki so finančne pogodbe, katerih vrednost temelji na osnovni kriptovaluti. Pogodbe o izvedenih finančnih instrumentih, kot so terminske pogodbe in opcije, ponujajo dodatne načine za dostop in trgovanje s kriptovalutami.

Seveda lahko vzamete tudi zaslužene obresti in jih uporabite kot hranilnik vrednosti. Kot sredstvo za shranjevanje vrednosti se pričakuje, da bo ta kriptovaluta ohranila svojo kupno moč za kasnejšo uporabo. Znane zaloge vrednosti vključujejo zlato, zato se najbolj priljubljena kriptovaluta, Bitcoin, pogosto imenuje "digitalno zlato". Pri trgovanju z izvedenimi finančnimi instrumenti je vrednost ocenjena na podlagi osnovnega sredstva. Osnovno sredstvo je lahko tudi kriptovaluta. 

Vsak vlagatelj potrebuje metodo primerjave naložbenih priložnosti in izračuna, koliko dobička je ustvaril. APY ali letni odstotek donosa je standardni izračun stopnje donosa, ki se uporablja v tradicionalnih financah in kriptovalutah. Vključuje učinke zapletenih obresti, ki lahko povečajo zasluženi znesek. Višji kot je APY, več denarja zaslužijo vlagatelji. Primerjava vaših možnosti APY vam lahko pomaga ugotoviti vaše najbolj privlačne naložbene priložnosti.

☞  Kaj je APR (letna odstotna stopnja) v Crypto?

Hvala za branje!

What is GEEK

Buddha Community

Top 10 API Security Threats Every API Team Should Know

As more and more data is exposed via APIs either as API-first companies or for the explosion of single page apps/JAMStack, API security can no longer be an afterthought. The hard part about APIs is that it provides direct access to large amounts of data while bypassing browser precautions. Instead of worrying about SQL injection and XSS issues, you should be concerned about the bad actor who was able to paginate through all your customer records and their data.

Typical prevention mechanisms like Captchas and browser fingerprinting won’t work since APIs by design need to handle a very large number of API accesses even by a single customer. So where do you start? The first thing is to put yourself in the shoes of a hacker and then instrument your APIs to detect and block common attacks along with unknown unknowns for zero-day exploits. Some of these are on the OWASP Security API list, but not all.

Insecure pagination and resource limits

Most APIs provide access to resources that are lists of entities such as /users or /widgets. A client such as a browser would typically filter and paginate through this list to limit the number items returned to a client like so:

First Call: GET /items?skip=0&take=10 
Second Call: GET /items?skip=10&take=10

However, if that entity has any PII or other information, then a hacker could scrape that endpoint to get a dump of all entities in your database. This could be most dangerous if those entities accidently exposed PII or other sensitive information, but could also be dangerous in providing competitors or others with adoption and usage stats for your business or provide scammers with a way to get large email lists. See how Venmo data was scraped

A naive protection mechanism would be to check the take count and throw an error if greater than 100 or 1000. The problem with this is two-fold:

1. For data APIs, legitimate customers may need to fetch and sync a large number of records such as via cron jobs. Artificially small pagination limits can force your API to be very chatty decreasing overall throughput. Max limits are to ensure memory and scalability requirements are met (and prevent certain DDoS attacks), not to guarantee security.
2. This offers zero protection to a hacker that writes a simple script that sleeps a random delay between repeated accesses.

skip = 0
while True:    response = requests.post('https://api.acmeinc.com/widgets?take=10&skip=' + skip),                      headers={'Authorization': 'Bearer' + ' ' + sys.argv[1]})    print("Fetched 10 items")    sleep(randint(100,1000))    skip += 10

How to secure against pagination attacks

To secure against pagination attacks, you should track how many items of a single resource are accessed within a certain time period for each user or API key rather than just at the request level. By tracking API resource access at the user level, you can block a user or API key once they hit a threshold such as “touched 1,000,000 items in a one hour period”. This is dependent on your API use case and can even be dependent on their subscription with you. Like a Captcha, this can slow down the speed that a hacker can exploit your API, like a Captcha if they have to create a new user account manually to create a new API key.

Insecure API key generation

Most APIs are protected by some sort of API key or JWT (JSON Web Token). This provides a natural way to track and protect your API as API security tools can detect abnormal API behavior and block access to an API key automatically. However, hackers will want to outsmart these mechanisms by generating and using a large pool of API keys from a large number of users just like a web hacker would use a large pool of IP addresses to circumvent DDoS protection.

How to secure against API key pools

The easiest way to secure against these types of attacks is by requiring a human to sign up for your service and generate API keys. Bot traffic can be prevented with things like Captcha and 2-Factor Authentication. Unless there is a legitimate business case, new users who sign up for your service should not have the ability to generate API keys programmatically. Instead, only trusted customers should have the ability to generate API keys programmatically. Go one step further and ensure any anomaly detection for abnormal behavior is done at the user and account level, not just for each API key.

Accidental key exposure

APIs are used in a way that increases the probability credentials are leaked:

1. APIs are expected to be accessed over indefinite time periods, which increases the probability that a hacker obtains a valid API key that’s not expired. You save that API key in a server environment variable and forget about it. This is a drastic contrast to a user logging into an interactive website where the session expires after a short duration.
2. The consumer of an API has direct access to the credentials such as when debugging via Postman or CURL. It only takes a single developer to accidently copy/pastes the CURL command containing the API key into a public forum like in GitHub Issues or Stack Overflow.
3. API keys are usually bearer tokens without requiring any other identifying information. APIs cannot leverage things like one-time use tokens or 2-factor authentication.

If a key is exposed due to user error, one may think you as the API provider has any blame. However, security is all about reducing surface area and risk. Treat your customer data as if it’s your own and help them by adding guards that prevent accidental key exposure.

How to prevent accidental key exposure

The easiest way to prevent key exposure is by leveraging two tokens rather than one. A refresh token is stored as an environment variable and can only be used to generate short lived access tokens. Unlike the refresh token, these short lived tokens can access the resources, but are time limited such as in hours or days.

The customer will store the refresh token with other API keys. Then your SDK will generate access tokens on SDK init or when the last access token expires. If a CURL command gets pasted into a GitHub issue, then a hacker would need to use it within hours reducing the attack vector (unless it was the actual refresh token which is low probability)

Exposure to DDoS attacks

APIs open up entirely new business models where customers can access your API platform programmatically. However, this can make DDoS protection tricky. Most DDoS protection is designed to absorb and reject a large number of requests from bad actors during DDoS attacks but still need to let the good ones through. This requires fingerprinting the HTTP requests to check against what looks like bot traffic. This is much harder for API products as all traffic looks like bot traffic and is not coming from a browser where things like cookies are present.

Stopping DDoS attacks

The magical part about APIs is almost every access requires an API Key. If a request doesn’t have an API key, you can automatically reject it which is lightweight on your servers (Ensure authentication is short circuited very early before later middleware like request JSON parsing). So then how do you handle authenticated requests? The easiest is to leverage rate limit counters for each API key such as to handle X requests per minute and reject those above the threshold with a 429 HTTP response. There are a variety of algorithms to do this such as leaky bucket and fixed window counters.

Incorrect server security

APIs are no different than web servers when it comes to good server hygiene. Data can be leaked due to misconfigured SSL certificate or allowing non-HTTPS traffic. For modern applications, there is very little reason to accept non-HTTPS requests, but a customer could mistakenly issue a non HTTP request from their application or CURL exposing the API key. APIs do not have the protection of a browser so things like HSTS or redirect to HTTPS offer no protection.

How to ensure proper SSL

Test your SSL implementation over at Qualys SSL Test or similar tool. You should also block all non-HTTP requests which can be done within your load balancer. You should also remove any HTTP headers scrub any error messages that leak implementation details. If your API is used only by your own apps or can only be accessed server-side, then review Authoritative guide to Cross-Origin Resource Sharing for REST APIs

Incorrect caching headers

APIs provide access to dynamic data that’s scoped to each API key. Any caching implementation should have the ability to scope to an API key to prevent cross-pollution. Even if you don’t cache anything in your infrastructure, you could expose your customers to security holes. If a customer with a proxy server was using multiple API keys such as one for development and one for production, then they could see cross-pollinated data.

#api management #api security #api best practices #api providers #security analytics #api management policies #api access tokens #api access #api security risks #api access keys

Public ASX100 APIs: The Essential List

We’ve conducted some initial research into the public APIs of the ASX100 because we regularly have conversations about what others are doing with their APIs and what best practices look like. Being able to point to good local examples and explain what is happening in Australia is a key part of this conversation.

Method

The method used for this initial research was to obtain a list of the ASX100 (as of 18 September 2020). Then work through each company looking at the following:

1. Whether the company had a public API: this was found by googling “[company name] API” and “[company name] API developer” and “[company name] developer portal”. Sometimes the company’s website was navigated or searched.
2. Some data points about the API were noted, such as the URL of the portal/documentation and the method they used to publish the API (portal, documentation, web page).
3. Observations were recorded that piqued the interest of the researchers (you will find these below).
4. Other notes were made to support future research.
5. You will find a summary of the data in the infographic below.

Data

With regards to how the APIs are shared:

• Documentation is where just the Swagger/OpenAPI docs are hosted somewhere. e.g. https://api.linkgroup.com/member/docs/index
• Portal is where an interactive portal has been developed. e.g. https://dev.telstra.com/
• The web page is where the company has a single page that isn’t interactive explaining their Public APIs. e.g. https://www.bendigoadelaide.com.au/banking-products-api.asp

#api #api-development #api-analytics #apis #api-integration #api-testing #api-security #api-gateway

An API-First Approach For Designing Restful APIs | Hacker Noon

I’ve been working with Restful APIs for some time now and one thing that I love to do is to talk about APIs.

So, today I will show you how to build an API using the API-First approach and Design First with OpenAPI Specification.

First thing first, if you don’t know what’s an API-First approach means, it would be nice you stop reading this and check the blog post that I wrote to the Farfetchs blog where I explain everything that you need to know to start an API using API-First.

Preparing the ground

Before you get your hands dirty, let’s prepare the ground and understand the use case that will be developed.

Tools

If you desire to reproduce the examples that will be shown here, you will need some of those items below.

• NodeJS
• OpenAPI Specification
• Text Editor (I’ll use VSCode)
• Command Line

Use Case

To keep easy to understand, let’s use the Todo List App, it is a very common concept beyond the software development community.

#api #rest-api #openai #api-first-development #api-design #apis #restful-apis #restful-api

What Are Good Traits That Make Great API Product Managers

As more companies realize the benefits of an API-first mindset and treating their APIs as products, there is a growing need for good API product management practices to make a company’s API strategy a reality. However, API product management is a relatively new field with little established knowledge on what is API product management and what a PM should be doing to ensure their API platform is successful.

Many of the current practices of API product management have carried over from other products and platforms like web and mobile, but API products have their own unique set of challenges due to the way they are marketed and used by customers. While it would be rare for a consumer mobile app to have detailed developer docs and a developer relations team, you’ll find these items common among API product-focused companies. A second unique challenge is that APIs are very developer-centric and many times API PMs are engineers themselves. Yet, this can cause an API or developer program to lose empathy for what their customers actually want if good processes are not in place. Just because you’re an engineer, don’t assume your customers will want the same features and use cases that you want.

This guide lays out what is API product management and some of the things you should be doing to be a good product manager.

#api #analytics #apis #product management #api best practices #api platform #api adoption #product managers #api product #api metrics

54% of Developers Cite Lack of Documentation as the Top Obstacle to Consuming APIs

Recently, I worked with my team at Postman to field the 2020 State of the API survey and report. We’re insanely grateful to the folks who participated—more than 13,500 developers and other professionals took the survey, helping make this the largest and most comprehensive survey in the industry. (Seriously folks, thank you!) Curious what we learned? Here are a few insights in areas that you might find interesting:

API Reliability

Whether internal, external, or partner, APIs are perceived as reliable—more than half of respondents stated that APIs do not break, stop working, or materially change specification often enough to matter. Respondents choosing the “not often enough to matter” option here came in at 55.8% for internal APIs, 60.4% for external APIs, and 61.2% for partner APIs.

Obstacles to Producing APIs

When asked about the biggest obstacles to producing APIs, lack of time is by far the leading obstacle, with 52.3% of respondents listing it. Lack of knowledge (36.4%) and people (35.1%) were the next highest.

#api #rest-api #apis #api-first-development #api-report #api-documentation #api-reliability #hackernoon-top-story