Relationships used to be one sided (IE the source object would store a reference of all destinations) and that was it. This ended up being problematic as relationships could only be explored from one side, which is problematic, especially from tools like Maltego. As a result I changed it so creating a new relationship it adds the reference to both objects, so they can be found from either direction.
While I was at it I added API endpoints for both getting a relationship (based on one end point) and creating a relationship (based on providing both endpoints).
I'm sure I'm missing some of the error conditions and things like that, but it's getting started.
Relationships used to be one sided (IE the source object would store a reference of all destinations) and that was it. This ended up being problematic as relationships could only be explored from one side, which is problematic, especially from tools like Maltego. As a result I changed it so creating a new relationship it adds the reference to both objects, so they can be found from either direction.
While I was at it I added API endpoints for both getting a relationship (based on one end point) and creating a relationship (based on providing both endpoints).
I'm sure I'm missing some of the error conditions and things like that, but it's getting started.