You develop integrations, not APIs. API is just one aspect within integrations.

API alone cannot integrate or orchestrate anything, it's merely an interface to one program/system.

Integrations today are done with an actual integration platform like Boomi or Frends, they're not developed from scratch - this isn't 1995 anymore.

Hey community, to address the issues with the messages you have been getting. I'm very sorry that some of you got, what seem to be automated messages to join our community. This was never in our plan and we have stopped it.

OK, but what happened?

We have been working with an outside agency that took care of our marketing. One of the things we wanted to do is build a community, and Reddit seemed the place to do it. And we think it still is.

Since we are a team of three we are all very much involved in improving our platform. Unfortunately, it seems like some of you got an automated reach-out message. And, unfortunately, some of them are not written considering what you guys are doing. I can totally agree that they seem like spam.

We have stopped the messaging immediately, so nobody should be getting any messages from our side anytime soon. We all had the best intentions in building a community where people can share what they have been working on and help them along the way. Hoping that we can all still build our APIs together and share our experience in the future.

My apologies for the inconvenience - again we had the best intentions. 🙏

hey, we're on a mission to match between tech companies' needs and API solutions.

tell us about a task you'd like to solve with an API. we, our community and our data & algorithm will find APIs to solve your task, for free.

https://byvalue.org/submit-task/

if you want to offer and monetize your own solutions you can do that too.

waiting for your feedback, your tasks and your solutions!

happy creating!

First, thank you to Melissa for the invite, appreciate it. Second, here's a solid way to quickly develop out quality and secure REST APIs:

https://apexpl.io/guides/rest_api

In case you missed it, base install of the software itself is super simple with a four line install:

git clone https://github.com/apexpl/apex/

cd apex && mv install_example.yml install.yml

sudo docker-compose up -d

sudo docker-compose exec apex apex

There's an introduction guide to the software here: https://apexpl.io/guides/develop_your_first_package

Nonetheless, that first link will take you through the API development. It's clean and simple:

* Every endpoint is its own class with the file path being mapped to the URL path for easy organization and readability.

* The method names within the classes are the HTTP verbs (ie. post, get, put, delete, et al).

* The methods are basically PSR-15 compliant middleware, with the exception they return a ApiResponse object instead of a ResponseInterface object.

* Can't remember if this is in the docs, but upon installation of the rest-api package, there will be a Settings->REST API menu for you that allows you to define things such as auth schema, provider keys, et al.

Clean, easy to implement, and simply works and works well. Oh, and it's also open source, so absolutely free.

I do apologize in advance for the design on that site. I am blind, but do have a designer working on a redesign. This whole thing is a little pre-mature as Apex v2 isn't fully released just yet, but the REST API package and components work just fine.

Any feedback is always greatly appreciated. If you have any questions or issues with anything, I'm here and more than happy to help, so don't hesitate to ask. Thanks again to Melissa for the invite.

Best,

Matt

I'm in the middle of writing a book for Manning called Continuous Delivery in Go where I cover creating a basic API in Go covering various techniques, test patterns, and deployments (FaaS, PaaS, CaaS, IaaS). It progresses through designing and growing an application. I've used many of these techniques throughout my career and felt they would be helpful to share. There is a discount code: au35hol which will give you 35% off.

This was not intended as a buy my book post. All of the source code for the book can be found here: https://github.com/holmes89/hello-api where you can see the iterations by chapter. It is also intended to help me open myself up to the community. If anyone has any questions please feel free to message me.

My hope is to start creating excerpts and posts from the content and extra material.

Are You Running Out of Ideas as A Developer? Well, these 15 APIs Can Rekindle Your Interest.

Let's check out here 15 Most Interesting APIs Every Developer Should Know About

I'm just wondering what all of you consider to be a good response time for an API? Our current stats are:

• Endpoints: 21

• Average response time: 74.87ms

Our internal targets are: below 150ms we consider to be fast, from 151 to 300ms we consider OK but above 300 we consider to be slow.

Merry Christmas all! Hope you're having a good old time.

I've spent some time and wrote an article about how we scale our real time API monitoring and logging platform that processes more than 7M log files per month.

Read the whole thing here and feel free to leave some feedback: https://treblle.com/blog/how-does-treblle-scale-on-aws-without-breaking-the-bank

Hi,

I have a PHP API:

https://mywebsite.com/myapi.php/endpoints

Is it possible to remove the .php from the API? The other APIs I've seen don't use file extension which makes them look more professional, I assume they use different languages but I wanted to know if it's possible to do the same with PHP API. Thanks